On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins <de...@ihtfp.com> wrote:

> Hi,
> I've got ovirt running on a single host (with hosted-engine).  I just
> upgraded the engine from 4.0.4 to 4.0.5.  That was pretty easy; I just
> put the system into global maintenance mode, then yum update, then
> engine-setup, then took the host out of maint mode.  Easy peasy.

'took the host out of maint' -> took the engine VM out of maintenance mode:
global maintenance mode means that ovirt-ha-agent (on any hosts) will not
try to check, restart, migrate... the engine VM.

> Now, I want to update the host itself.  Since it's a single host system
> I know I'll need to shut down all the VMs (because there's no place to
> migrate them).  This means I'll need to shut down the engine VM, too.
> That would imply that I can't use the "Update" feature from the ui,
> right?

Yes, correct

> So what IS the process to properly update a single-host host?  My guess
> is:
> * shutdown all the VMs
* go into global maint mode (what IS the difference between global and
>   local?)
> * shutdown the engine/engine VM
> * yum update on the host
> * restart services (or reboot, I guess)
> * bring the system out of maintenance mode

shutdown or hibernate all the other VMs.
set global maintenance mode to avoid ovirt-ha-agent trying to restart the
engine vm
shutdown the engine VM (from the host CLI) with hosted-engine --vm-shutdown
yum update
restart services
bring the system out of global maintenance mode: in a couple of minutes the
HA agent should restart the engine VM

> Am I missing a step?  Do I need to run hosted-engine --deploy again
> similar to how I needed to run "engine-setup" on the engine?  Or is
> there something else I need to run?
> Thanks,
> -derek
> --
>        Derek Atkins                 617-623-3745
>        de...@ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
Users mailing list

Reply via email to