<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 23, 2017 at 6:51 PM, Claude Duropcher <span dir="ltr"><<a href="mailto:claude.durocher@cptaq.gouv.qc.ca" target="_blank">claude.durocher@cptaq.gouv.qc.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Simone, thanks for replying,<br>
</p>
<p>According to the documentation, global mode seems to be a
superset of local mode. Does setting to local mode maintenance on
all hosts in the cluster really bring any benefits?<br></p></div></blockquote><div><br></div><div>No, not really: they are different and global is not superset of local.</div><div>global maintenance mode is needed if you need to do maintenance on the engine VM, no host will restart the engine VM. local maintenance mode is if you need to do maintenance or upgrade a single host.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><p>
</p>
<ul>
<li>
<p><code>global</code> - All high-availability agents in the
cluster are disabled from monitoring the state of the engine
virtual machine. The global maintenance mode must be applied
for any setup or upgrade operations that require the engine to
be stopped, such as upgrading to a later version of oVirt.</p>
</li>
<li>
<p><code>local</code> - The high-availability agent on the host
issuing the command is disabled from monitoring the state of
the engine virtual machine. The host is exempt from hosting
the engine virtual machine while in local maintenance mode; if
hosting the engine virtual machine when placed into this mode,
the engine will be migrated to another host, provided there is
a suitable contender. The local maintenance mode is
recommended when applying system changes or updates to the
host.</p>
</li>
</ul><div><div class="h5">
<div class="m_8034082363097501398moz-cite-prefix">Le 2017-01-23 à 12:13, Simone
Tiraboschi a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 23, 2017 at 4:20 PM,
Claude Duropcher <span dir="ltr"><<a href="mailto:claude.durocher@cptaq.gouv.qc.ca" target="_blank">claude.durocher@cptaq.gouv.<wbr>qc.ca</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
We need to update/reboot the NFS server on wich the hosted
engine is installed. This server also hosts a couple of
extra storage domains (ISO, Export and a iScsi domain).
I'm wondering if this procedure is complete for an oVirt
4.0 installation :<br>
<br>
1-set the environment to global maintenance<br>
<br>
2-set the extra domains to maintenance mode<br>
<br>
3-shutdown the hosted engine<br>
<br>
4-update/reboot the storage server<br>
<br>
5-reboot the hosted engine<br>
<br>
6-reactivate extra domains<br>
<br>
7-disable global maintenance mode<br>
<br>
I'm wondering what's happening after step 4 and how ovirt
will react when the NFS storage disapear and come back.<br>
<br>
</blockquote>
<div><br>
</div>
<div>ovirt-ha-agent will try to reconnect the shared storage
if hosted-engine for all the time; depending on different
factors, sanlock will fail updating the hosted-engine
lease ans this can bring the watchdog to reboot the host.</div>
<div>Setting also local maintenance mode on the involved
hosts is a good idea.</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div>