<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Sep 4, 2016 at 10:54 AM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.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"><span class="gmail-">On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi<br>
<<a href="mailto:gianluca.cecchi@gmail.com">gianluca.cecchi@gmail.com</a>> wrote:<br>
> Hello,<br>
> how do the two modes apply in case of single host?<br>
> During an upgrade phase, after having upgraded the self hosted engine and<br>
> leaving global maintenance and having checked all is ok, what is the correct<br>
> mode then to put host if I want finally to update it too?<br>
<br>
</span>The docs say to put hosts to maintenance from the engine before upgrading them.<br>
<br>
This is (also) so that VMs on them are migrated away to other hosts.<br>
<br>
With a single host, you have no other hosts to migrate VMs to.<br>
<br>
So you should do something like this:<br>
<br>
1. Set global maintenance (because you are going to take down the<br>
engine and its vm)<br>
2. Shutdown all other VMs<br>
3. Shutdown engine vm from itself<br>
At this point, you should be able to simply stop HA services. But it<br>
might be cleaner to first set local maintenance. Not sure but perhaps<br>
this might be required for vdsm. So:<br>
4. Set local maintenance<br>
5. Stop HA services. If setting local maintenance didn't work, perhaps<br>
better stop also vdsm services. This stop should obviously happen<br>
automatically by yum/rpm, but perhaps better do this manually to see<br>
that it worked.<br>
6. yum (or dnf) update stuff.<br>
7. Start HA services<br>
8. Check status. I think you'll see that both local and global maint<br>
are still set.<br>
9. Set maintenance to none<br>
10. Check status again - I think that after some time HA will decide<br>
to start engine vm and should succeed.<br>
11. Start all other VMs.<br>
<br>
Didn't try this myself.<br>
<br>
Best,<br>
<span class="gmail-HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">Hello Didi,</div><div class="gmail_extra">I would like to leverage the update I have to do on 2 small different lab environments to crosscheck the steps suggested.</div><div class="gmail_extra">They are both single host environments with self hosted engine.</div><div class="gmail_extra">One is 4.0.2 and the other is 4.0.3. Both on CentoS 7.2</div><div class="gmail_extra">I plan to migrate to the just released 4.0.4</div><div class="gmail_extra"><br></div><div class="gmail_extra">One note: in both environments the storage is NFS and is provided by the host itself, so a corner case (for all hosted_storage domain, main data domain and iso storage domain).</div><div class="gmail_extra">I customized the init scripts, basically for start phase of the server and to keep in count of the NFS service, but probably something has to be done for stop too?</div><div class="gmail_extra"><br></div><div class="gmail_extra">1) In /usr/lib/systemd/system/ovirt-ha-broker.service</div><div class="gmail_extra"><br></div><div class="gmail_extra">added in section [Unit]</div><div class="gmail_extra"><br></div><div class="gmail_extra">After=nfs-server.service</div><div class="gmail_extra"><br></div><div class="gmail_extra">The file is overwritten at update so one has to keep in mind this</div><div class="gmail_extra"><br></div><div class="gmail_extra">2) also in vdsmd.service changed </div><div class="gmail_extra">from:</div><div class="gmail_extra"><div class="gmail_extra">After=multipathd.service libvirtd.service iscsid.service rpcbind.service \</div><div class="gmail_extra"> supervdsmd.service sanlock.service vdsm-network.service</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">to:</div><div class="gmail_extra">After=multipathd.service libvirtd.service iscsid.service rpcbind.service \<br></div><div class="gmail_extra"><div class="gmail_extra"> supervdsmd.service sanlock.service vdsm-network.service \</div><div class="gmail_extra"> nfs-server.service</div><div><br></div><div>Do you think any order setup I have to put in place related to NFS service and oVirt services stop?</div></div><div><br></div></div>