<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Jan 23, 2017 3:20 PM, "Nathanaël Blanchet" <<a href="mailto:blanchet@abes.fr">blanchet@abes.fr</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div class="quoted-text">
<p><br>
</p>
<br>
<div class="m_7917627718603981592moz-cite-prefix">Le 23/01/2017 à 13:08, Yaniv Kaul 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 1:38 PM,
Nathanaël Blanchet <span dir="ltr"><<a href="mailto:blanchet@abes.fr" target="_blank"></a><a class="m_7917627718603981592moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr" target="_blank">blanchet@abes.fr</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>
The update notifier in the webadmin was originally
designed to alert for new vdsm* packages. Now, I noticed
that available update of virt packages and more are
notified. I know that hot updating qemu-kvm package does
break vms that are running on concerned hosts, but what
about other one like libvirt-client? I know it is
recommended to put in maintenance while updating, but can
we update some minor packages without waiting for
migration?<br>
</blockquote>
<div><br>
</div>
<div>Hot-updating any package should not break any running
VMs. If it does, it's a bug.</div>
</div>
</div>
</div>
</blockquote></div>
The last time I did a qemu-kvm upgrade, my host became down and the
vms on it with a question mark and no possibility to interact with
them. My only solution was to use the "confirm host has rebooted" to
fence the vms, and then the nightmare began : the high</div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Was the host indeed rebooted? </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"> availaible
vms rebooted on an other host while they were still active on the
first one, so they were up on two hosts at the same time. Their disk
began to be written by two vms at the same time and I had to fscsk
them to make them up on the next boot. Some database vms were
completely unusabled!<br></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">On 4.1 we are going to introduce a feature that will protect against this situation, by taking a lock on the storage. </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<br>
So I'm very surprised to hear that it is possible to do
hot-updating on these kind of upgrade, and I won't do it anymore!<div class="elided-text"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>I personally agree it's not the best habit to do it
nevertheless, and I expect users to put hosts to
maintenance before performing any upgrade.</div>
<div><br>
</div>
<div>We cannot tell which update requires maintenance and
which doesn't (or for that matter - requires a reboot or a
service restart) - there's no metadata available to do
attached to the packages that can tell us that.</div>
<div>Y.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
-- <br>
Nathanaël Blanchet<br>
<br>
Supervision réseau<br>
Pôle Infrastrutures Informatiques<br>
227 avenue Professeur-Jean-Louis-Viala<br>
34193 MONTPELLIER CEDEX 5 <br>
Tél. 33 (0)4 67 54 84 55<br>
Fax 33 (0)4 67 54 84 14<br>
<a href="mailto:blanchet@abes.fr" target="_blank">blanchet@abes.fr</a><br>
<br>
______________________________<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>
<pre class="m_7917627718603981592moz-signature" cols="72">--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
<a class="m_7917627718603981592moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr" target="_blank">blanchet@abes.fr</a> </pre>
</div></div>
</blockquote></div><br></div></div></div>