On Thu, Sep 20, 2018 at 9:08 AM Gary Pedretty <gary(a)flyravn.com&gt; wrote: Set global maintenance mode, update the engine VM as a regular installation, exit the global maintenance mode at the end. If you need to reboot the engine vm you can still hosted-engine --vm-start also while in global maintenance mode.

Ok that is what I have done in the past, sometimes it works, sometimes the engine ends up corrupted and I have had to re-deploy it. thanks Gary __________________ [cid:D51E31D3-90B6-4306-BCC8-4DA475005073] On Sep 20, 2018, at 1:48 AM, Jayme <jaymef@gmail.com<mailto:jaymef@gmail.com>> wrote: Upgrading the engine is fairly straight forward. What I do is place the cluster in global maintenance mode. Then on the engine vm yum update Ovirt packages then run engine-upgrade. After upgrade I do a general yum update on engine vm to update other non Ovirt packages On Thu, Sep 20, 2018, 4:07 AM Gary Pedretty, <gary@flyravn.com<mailto:gary@flyravn.com>> wrote: What is the official recommended method in a Hosted Engine Data Center/Cluster to upgrade the hosted_engine VM. Applying the updates on the individual hosts is pretty straight forward using either the GUI or just running yum update on each host once they are in maintenance mode. But what about the engine? This is an engine vm that was created from the appliance rpm initially. The documentation seems to skip over applying the periodic updates except to the individual hosts. Thanks Gary __________________ _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto: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/FTHSBZ6L6K6...