<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 15, 2017 at 3:39 PM, Derek Atkins <span dir="ltr"><<a href="mailto:derek@ihtfp.com" target="_blank">derek@ihtfp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
FWIW, I'm running on a single-host system with hosted-engine.<br></blockquote></div><br></div><div class="gmail_extra">I made the same update on two single host environments with self hosted engine without any problem.<br></div><div class="gmail_extra">My approach was;<br></div><div class="gmail_extra"><br>- shutdown all VMs except self hosted engine<br></div><div class="gmail_extra">- put environment in global maintenance<br></div><div class="gmail_extra">- update the self hosted engine environment<br></div><div class="gmail_extra">(with commands:<br>yum update "ovirt-*-setup*"<br></div><div class="gmail_extra">engine-setup<br></div><div class="gmail_extra">)<br></div><div class="gmail_extra">- verify connection to engine web admin gui is still ok and 4.0.6. Engine os at this time is still 7.2<br></div><div class="gmail_extra">- shutdown engine VM<br></div><div class="gmail_extra">- put hypervisor host in local maintenance<br></div><div class="gmail_extra">- stop some services (ovirt-ha-agent, ovirt-ha-broker, vdsmd)<br></div><div class="gmail_extra">- run yum update that brings hypervisor at 7.3 and also new vdsm and related packages to 4.0.6 level and also qemu-kvm-ev at 2.6.0-27.1.el7<br></div><div class="gmail_extra">- adjust/merge some rpmnew files (both os in general and ovirt related)<br></div><div class="gmail_extra">- stop again vdsmd (agent and broker remained down)<br></div><div class="gmail_extra">- stop sanlock (here sometimes it goes timeout so I "kill -9" the remaining process otherwise the system is unable to shutdown due to impossibility to umount nfs filesystems<br></div><div class="gmail_extra">In fact in my environment the host itself provides nfs mounts for data storage domain and iso one; the umount problem is only with the data one)<br></div><div class="gmail_extra">- shutdown host and reboot it<br></div><div class="gmail_extra">- exit maintenance<br></div><div class="gmail_extra">- engine vm starts after a while<br></div><div class="gmail_extra">- enter global maintenance again <br></div><div class="gmail_extra">- yum update on engine vm and adjust rpmnew files<br></div><div class="gmail_extra">- shutdown engine vm<br></div><div class="gmail_extra">- exit global maintenance<br></div><div class="gmail_extra">- after a while engine vm starts<br></div><div class="gmail_extra">- power on VMs required.<br><br></div><div class="gmail_extra">Gianluca<br></div></div>