[ovirt-users] the better way to update vdsm

[Dan Kenigsberg]

On Wed, Sep 24, 2014 at 11:30:03AM +0000, Daniel Helgenberger wrote:
> Hello Nathanaël,
> 
> I think the supposed way to upgrade would be:
> 
> * (hosted-engine only) put cluster in global maintenance if running
> hosted-enfgine
> * upgrade Engine using engine-setup (this *should* detect product updates)
> * (hosted-engine only) disable global maintenance
> * Put host in maintenance mode (witch will migrate VMs automatically)
> * Click 'reinstall host' in Engine (this step will will invoke yum update?)
> * Activate host
> 
> continue with the other hosts
> 
> 
> If there are kernel updates, I usually update them as well in the
> process (involving manual yum).
> 
> Can anyone clarify if 'reinstall host' invokes yum? Thanks!
> 
> 
> On 24.09.2014 11:41, Nathanaël Blanchet wrote:
> > Hi all,
> >
> > I'm about to update to 3.4.4 with the associated vdsm. Updating vdsm with yum is 
> > trivial, but it usually breaks running vms on the host.
> > So these are the steps I follow each time:
> >
> >   * live migrating runnings vms to a another host in the cluster
> >   * putting the host in maintenance
> >   * updating vdsm
> >   * activating the host

That's the prudent thing to do, but `yum upgrade vdsm` should NOT "break
vms". When it does, I'd love to see a bug report (VMs being temporarily
paused due to lost storage is expected).