[ovirt-users] Ovirt-3.4.1: How to: Upgrading Hosted Engine Cluster

[Doron Fediuck]

----- Original Message -----
> From: "Darrell Budic" <darrell.budic at zenfire.com>
> To: "Doron Fediuck" <dfediuck at redhat.com>
> Cc: "users" <users at ovirt.org>
> Sent: Monday, May 12, 2014 10:15:53 PM
> Subject: Re: [ovirt-users] Ovirt-3.4.1: How to: Upgrading Hosted Engine Cluster
> 
> 
> On May 10, 2014, at 1:47 AM, Doron Fediuck <dfediuck at redhat.com> wrote:
> 
> > 
> > 
> > ----- Original Message -----
> >> From: "Daniel Helgenberger" <daniel.helgenberger at m-box.de>
> >> To: users at ovirt.org
> >> Sent: Friday, May 9, 2014 6:45:36 PM
> >> Subject: [ovirt-users] Ovirt-3.4.1: How to: Upgrading Hosted Engine
> >> Cluster
> >> 
> >>     1. Set cluster to global maintance
> >>     2. Login to ovit engine and to the upgrade according to the release
> >>        nodes.
> >>     3. After the upgrade is finished and the engine running, set the
> >>        first Node in local maintenance.
> >>     4. Login the first node and yum update (with the removal of
> >>        ovirt-release as mentioned in release notes).* I rebooted the
> >>        node because of the kernel update.
> >>     5. Return to oVirt and reinstall the Node from GUI, it will be set
> >>        to operational automatically**
> >>     6. Repeat steps 3-6 for the rest of the Nodes.
> >>     7. Remove global maintenance.
> >>     8. Update the last Node.***
> >> 
> > 
> > Hi Martin,
> > Thanks for sharing!
> > 
> > A few notes on your nice 8 steps ;)
> > 
> > - There are 2 maintenance modes to cover host maintenance (local) and
> >  VM maintenance (global). Global maintenance disarms all HA hosts in
> >  the cluster, so use it with caution as there's no fail over in this
> >  mode.
> > 
> > - Initially these were available only as a command line[1]. Since 3.4.0,
> >  this was integrated into the UI, so all you need to do is move a host
> >  to maintenance in order to achieve local maintenance, and activate it
> >  to remove the maintenance mode. For global maintenance, right click
> >  the engine VM, and you will see enable/disable ha-maintenance for
> >  the global mode.
> > 
> > - No need to re-install nodes. All you need to do is activate it.
> > 
> > - Basically a standard procedure should include:
> >  * Move host to maintenance, login and update the host, activate the host.
> >  * Follow the above for all other HA hosts
> >  * Set the engine VM to ha maintenance (global), login to the vm and
> >    upgrade it, unset vm's ha-maintenance.
> > 
> > Appreciate your feedback.
> > Also, were you aware of [1] or did you look for info elsewhere? I'd like
> > to know what we can do to improve documentation.
> 
> One thing that’s still unclear to me in this this setup is what’s needed to
> ensure all the nodes or get updates? Just do yum updates? I’ve have mixed
> success with the “reinstall or update” link in the GUI, seemed like it
> worked properly when I updated to 3.4.0, but trying to do the 3.4.1 update
> it failed for no apparent reason and I wound up doing yum updates on the
> host nodes…
> 
>   -Darrell
> 
> 

Hi Darrel,
the flow you described should work, and if not there's possibly a bug
in the host deployment. We need more details from your log files
to better understand what happened. For example, did you have your
repositories set correctly? Did you notice an error in the events pane?

The above scenario is generic regardless to manual or UI-based updates.

Doron