Anyone know if this is because they have an update scheduled tonight?
Or must we now switch to self-managed in order to refresh pilot?
Likely going to be a combination of both.
Currently live and pilot are at different patches which means you need to run a dot update after the refresh which requires it to be set to self managed.
However. You are also blocked from performing dot updates and changing the managed switch 48hrs before scheduled updates / upgrades up until the all clear message is posted.
3 Likes
Also is your live on windows and your pilot on linux?
Thanks Ben. Any idea if this is new validation rule enforcement? Pretty sure I’ve refreshed under these circumstances before.
I don’t believe it is new.
However. To be clear it is not the refresh that is blocked.
It is the fact that we are in an extended period of patch mismatch. Previously there would have been 3-4 days of mismatch not 4-5 weeks…
2 Likes
Yes. But we’ve done db refresh 3 times since pilot went linux.
1 Like
I ran into the same thing. I changed the options to Self-Managed, which allowed me to get past the first step where it was failing validation. But, it still errored out. I ended up having to put a ticket into Tech Support for them to do the refresh. I followed up on the ticket to see if I am supposed to be able to do this on my own (they said I was). I’ve probably done 7-8 refreshes of various environments over the last 6 months using CMP, I end up having to get Tech Support to run it more often than not.
3 Likes