
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 * getting back the vms * and so on with the other hosts...
But sometimes it is not enough, I need to reinstall the host so as to the host be able to successfully activate.
When getting back the vms on the initial host, I must do it manually to load balance vms between the hosts and this is not very convinient.
So my question is : do I update in the right way, or is there any recommendations that I didn't find anyway?
Thanks.
-- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767