>Why did you have to restart VMs for the migration to work ? Is it mandatory for an upgrade ?
I had to restart the VMs (even shutdown and start) for the raised compatibility level to kick in.
Migration works even if you don't restart VMs.
> Is it mandatory for an upgrade ?
No. But at some point you will have to or the VMs cluster compatibility level stays at the previous version.
Best regard, Mikhail
02.02.2017, 17:25, "Fernando Frediani" <fernando.fredi...@upx.com.br>:
Thanks for sharing your procedures.
Why did you have to restart VMs for the migration to work ? Is it mandatory for an upgrade ?
FernandoOn 02/02/2017 12:23, Краснобаев Михаил wrote:Hi,upgraded my cluster (3 hosts, engine, nfs-share) to the latest 4.1 release and Centos 7.3 (from 4.06).Did the following:1. Upgraded engine machine to Centos 7.32. Upgraded engine packages and ran "engine-setup"3. Upgraded one by one hosts to 7.3 + packages from the new 4.1. repo and refreshed hosts capabilities.4. Raised cluster and datacenter compatibility level to 4.1.5. Restarted virtual machines and tested migration.6. Profit! Everything went really smoothly. No errors.Now trying to figure out how the sparsify function works. I need to run trimming from inside the VM first?Best regards, Mikhail.02.02.2017, 15:19, "Sandro Bonazzola" <sbona...@redhat.com>:Hi,,did you install/update to 4.1.0? Let us know your experience!We end up knowing only when things doesn't work well, let us know it works fine for you :-)If you're not planning an update to 4.1.0 in the near future, let us know why.Maybe we can help.Thanks!----С уважением, Краснобаев Михаил._______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
С уважением, Краснобаев Михаил.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users