On Tue, Feb 5, 2019 at 8:24 AM Juhani Rautiainen
<juhani.rautiainen@gmail.com> wrote:
> Hi!
> Now that I have engine and nodes on 4.3 level I'm stuck on upgrading
> the CPU type. What is the correct way to solve this problem?
So it seems that I have to reinstall the whole cluster because usually
the silence means that there is no solution. As it currently stands I
don't see any other way. I made bugzilla entry about the problem
(1672859). This problem has been discussed shortly on this list 2016
but probably nobody bothered to do the bug report back then. Makes
upgrading hardware bit pointless if you can't use new CPU features.
You can simply upgrade the cluster if all the hosts are in global maintenance mode.
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
-Juhani
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/54K7BGQEWESN2DEIMZ55FIYQ7RLAIAZR/