On Wed, Feb 6, 2019 at 10:31 AM Simone Tiraboschi <stirabos@redhat.com> wrote:
You can simply upgrade the cluster if all the hosts are in global maintenance mode.
Like I originally wrote it doesn't work like that for me. This was what I tried. I tried again now and even confirmed from cli that it is correct mode: # hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! And still I get this: "Error while executing action: Cannot change Cluster CPU type unless all Hosts attached to this Cluster are in Maintenance" Is there a log where I can check if there are some traces why it gives this error message?
The only case that could prevent that is that you are in hosted-engine mode and so you cannot set the latest host into maintenance mode without loosing the engine itself.
If this is your case, what you can do is: - set HE global maintenance mode - set one of the hosted-engine hosts into maintenance mode - move it to a different cluster - shutdown the engine VM - manually restart the engine VM on the host on the custom cluster directly executing on that host: hosted-engine --vm-start - connect again to the engine - set all the hosts of the initial cluster into maintenance mode - upgrade the cluster - shut down again the engine VM - manually restart the engine VM on one of the hosts of the initial cluster - move back the host that got into a temporary cluster to its initial cluster
I might try this one. Thanks, Juhani