Hi, I always do it this way: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/... Never had issues with that. Even when I forget to put in global maintenance, the upgrade script will stop with an error about not being in maintenance mode. I have to say, I always use the RedHat documentation, it is quite good... BR Florian Von: "Simone Tiraboschi" <stirabos(a)redhat.com&gt; An: "Gary Pedretty" <gary(a)ravnalaska.net&gt; CC: "users" <users(a)ovirt.org&gt; Gesendet: Donnerstag, 20. September 2018 20:48:55 Betreff: [ovirt-users] Re: Hosted Engine Upgrades On Thu, Sep 20, 2018 at 6:32 PM Gary Pedretty < [ mailto:gary@ravnalaska.net | gary(a)ravnalaska.net ] > wrote: 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. Please double check you correctly set the global maintenance mode: engine-setup will stop the engine in order to upgrade it andif you are not in global maintenance mode, ovirt-ha-agent on the host will detect an engine failure and it will restart the engine VM in order to get a working engine. A VM reboot in the middle of the DB upgrade could corrupt it. BQ_BEGIN thanks Gary __________________ BQ_BEGIN On Sep 20, 2018, at 1:48 AM, Jayme < [ mailto:jaymef@gmail.com | jaymef(a)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, < [ mailto:gary@flyravn.com | gary(a)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 -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/FTHSBZ6L6K6... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/FTHSBZ6L6K6... ] BQ_END _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/RGD426VR7EY... | https://lists.ovirt.org/archives/list/users@ovirt.org/message/RGD426VR7EY... ] BQ_END _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/RTI2PKFBT2F...