<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Whups, yes, that was it:<div><br></div><div><div style="margin: 0px; position: static; z-index: auto;">MainThread::INFO::2014-02-28 17:23:03,546::hosted_engine::1311::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) Shutting down vm using `/usr/sbin/hosted-engine --vm-shutdown`</div><div style="margin: 0px;">MainThread::INFO::2014-02-28 17:23:04,500::hosted_engine::1315::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) stdout: Machine shut down</div><div><b><br></b></div><div>which also explains why I didn’t see anything in the engine logs, it was the self-hosted HA triggering the reboot when the engine shut down for the upgrade.. And I do remember the note about putting it into global maintenance before upgrading. Now ;)</div><div><br></div><div>Don’t know if the engine is aware it’s on a HA setup, if it it, might be a good thing to check for and maybe enable itself during the upgrade?</div><div><br></div><div>Are there any other special procedures to be aware of in a self-hosted setup? I haven’t tried updating the VDSM hosts for these yet, for instance. Seems like I shouldn’t enable global maintenance there, so the engine switches hosts properly?</div><div><br></div><div>Thanks.</div><div><br></div><div> -Darrell</div><div><br></div><div><div>On Mar 2, 2014, at 2:35 PM, Liviu Elama <<a href="mailto:liviu.elama@gmail.com">liviu.elama@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>Sounds like your hosts were not in maintenance mode while you were upgrading the engine which explains the 2 min reboot.<br><br></div>This should be revealed by logs <br><br></div>Regards <br>
</div>Liviu<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 2, 2014 at 10:32 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">----- Original Message -----<br>
> From: "Darrell Budic" <<a href="mailto:darrell.budic@zenfire.com">darrell.budic@zenfire.com</a>><br>
> To: "Sandro Bonazzola" <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>><br>
> Cc: <a href="mailto:announce@ovirt.org">announce@ovirt.org</a>, "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>>, "arch" <<a href="mailto:arch@ovirt.org">arch@ovirt.org</a>>, <a href="mailto:Users@ovirt.org">Users@ovirt.org</a>, "VDSM<br>
> Project Development" <<a href="mailto:vdsm-devel@lists.fedorahosted.org">vdsm-devel@lists.fedorahosted.org</a>><br>
> Sent: Saturday, March 1, 2014 1:56:23 AM<br>
> Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available<br>
><br>
> Started testing this on two self-hosted clusters, with mixed results. There<br>
> were updates from 3.4.0 beta 3.<br>
><br>
> On both, got informed the system was going to reboot in 2 minutes while it<br>
> was still installing yum updates.<br>
><br>
> On the faster system, the whole update process finished before the 2 minutes<br>
> were up, the VM restarted, and all appears normal.<br>
><br>
> On the other, slower cluster, the 2 minutes hit while the yum updates were<br>
> still being installed, and the system rebooted. It continued rebooting every<br>
> 3 minutes or so, and the engine console web pages are not available because<br>
> the engine doesn’t start. it did this at least 3 times before I went ahead<br>
> and reran engine-setup, which completed successfully. The system stopped<br>
> restarting and the web interface was available again. A quick perusal of<br>
> system logs and engine-setup logs didn’t reveal what requested the reboot.<br>
><br>
> That was rather impolite of something to do that without warning :) At least<br>
> it was recoverable. Seems like scheduling the reboot while the yum updates<br>
> were still running seems like a poor idea as well.<br>
<br>
Can you please post relevant logs?<br>
hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*,<br>
/var/log/vdsm/*<br>
engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/*<br>
<br>
You can of course open a bug on bugzilla and attach there logs if you want.<br>
<br>
Thanks, and thanks for the report!<br>
<span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</font></span></blockquote></div><br></div>
</blockquote></div><br></div></body></html>