Le 27 nov. 2024 à 14:01, dadamysus <dadamysus@proton.me> a écrit :
Hey Fabrice! Thanks for getting back! Got a few more questions
I have just finished a switch from oVirt 4.3 to oVirt 4.5 and CentOS 7 to Rocky 9.
The main gotcha is that the latest oVirt official release is broken, you should use the nightly build. You mean 4.5.5? In what way is it broken?
I was unable to reinstall or deploy new hosts, the installation phase failed, and it was bugs in oVirt.
I did it without downtime, but choose to reinstall the engine on a brand new server and restored the database. For each host, I put each of them in maintenance mode, reinstalled the OS on it and then reinstalled it in oVirt. How did you manage to do this without downtime? If you reinstalled the hosts how did you keep your VMs online?
The engine can be down without production impact, it runs on a dedicated server with it’s own life cycle. The VM keep running on the hosts, but of course you can’t change configuration or migrate them. I was able to reinstall hosts because I have a SAN, so I could move VM from one host to the other will reinstalling it and with no VM downtime.
Right now I have two nodes/hosts running on two different machines. Could I just do this: 1) Move all my VMs to one node. 2) Fully reinstall (new OS, oVirt engine) the empty host. 3) Backup the engine on the old host. 4) Import the backup on the new host. 5) Somehow get my VMs moved with or without downtime. 6) Reinstall the the second/old host.
But how would I get my VMs from the old to new host in this scenario?