<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 15, 2017 at 4:54 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> - update the self hosted engine environment<br>
> (with commands:<br>
> yum update "ovirt-*-setup*"<br>
> engine-setup<br>
> )<br>
<br>
</span>I did "yum update" and not "yum update "ovirt-*-setup*".. and...<br>
<span class=""><br>
> - verify connection to engine web admin gui is still ok and 4.0.6. Engine<br>
> os at this time is still 7.2<br>
<br>
</span>.... I updated the OS to 7.3 in the engine VM.<br>
<br>
I think that's the root of this bug, having PG restarted from under dwhd.<br>
The fact that your engine is still at 7.2 implies you didn't also perform<br>
the OS update on the engine. I wanted to do that. (Not sure why you<br>
didn't).<br>
<span class="HOEnZb"><font color="#888888"><br>
-derek<br></font></span></blockquote><div><br></div><div>See below, I did it at the end, after update of the host <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
</font></span><span class="im HOEnZb"><br>
> - shutdown engine VM<br>
> - put hypervisor host in local maintenance<br>
> - stop some services (ovirt-ha-agent, ovirt-ha-broker, vdsmd)<br>
> - run yum update that brings hypervisor at 7.3 and also new vdsm and<br>
> related packages to 4.0.6 level and also qemu-kvm-ev at 2.6.0-27.1.el7<br></span></blockquote><div>here for the host I used the approach of double update: os packages and oVirt packages<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="im HOEnZb">
> - adjust/merge some rpmnew files (both os in general and ovirt related)<br>
> - stop again vdsmd (agent and broker remained down)<br>
> - stop sanlock (here sometimes it goes timeout so I "kill -9" the<br>
> remaining<br>
> process otherwise the system is unable to shutdown due to impossibility to<br>
> umount nfs filesystems<br>
> In fact in my environment the host itself provides nfs mounts for data<br>
> storage domain and iso one; the umount problem is only with the data one)<br>
> - shutdown host and reboot it<br>
> - exit maintenance<br>
> - engine vm starts after a while<br>
> - enter global maintenance again<br>
> - yum update on engine vm and adjust rpmnew files<br></span></blockquote><div><br></div><div>here I have the step where I update the engine VM genaral os packages from 7.2 to 7.3...<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="im HOEnZb">
> - shutdown engine vm<br>
> - exit global maintenance<br>
> - after a while engine vm starts<br>
> - power on VMs required.<br>
><br>
> Gianluca<br>
><br>
<br>
<br>
</span><div class="HOEnZb"><div class="h5">--<br>
Derek Atkins 617-623-3745<br>
<a href="mailto:derek@ihtfp.com">derek@ihtfp.com</a> <a href="http://www.ihtfp.com" rel="noreferrer" target="_blank">www.ihtfp.com</a><br>
Computer and Internet Security Consultant<br>
<br>
</div></div></blockquote></div><br></div></div>