Re: [Users] hosted-engine rebooting in the middle of setup (was: [vdsm] [ANN] oVirt 3.4.0 Release Candidate is now available)
Whups, yes, that was it: 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` 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 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 ;) 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? 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? Thanks. -Darrell On Mar 2, 2014, at 2:35 PM, Liviu Elama liviu.el...@gmail.com wrote: Sounds like your hosts were not in maintenance mode while you were upgrading the engine which explains the 2 min reboot. This should be revealed by logs Regards Liviu On Sun, Mar 2, 2014 at 10:32 PM, Yedidyah Bar David d...@redhat.com wrote: - Original Message - From: Darrell Budic darrell.bu...@zenfire.com To: Sandro Bonazzola sbona...@redhat.com Cc: annou...@ovirt.org, engine-devel engine-de...@ovirt.org, arch a...@ovirt.org, Users@ovirt.org, VDSM Project Development vdsm-de...@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3. On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates. On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal. On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn’t start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn’t reveal what requested the reboot. That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well. Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* You can of course open a bug on bugzilla and attach there logs if you want. Thanks, and thanks for the report! -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] hosted-engine rebooting in the middle of setup (was: [vdsm] [ANN] oVirt 3.4.0 Release Candidate is now available)
- Original Message - From: Darrell Budic darrell.bu...@zenfire.com To: Sandro Bonazzola sbona...@redhat.com Cc: annou...@ovirt.org, engine-devel engine-de...@ovirt.org, arch a...@ovirt.org, Users@ovirt.org, VDSM Project Development vdsm-de...@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3. On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates. On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal. On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn’t start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn’t reveal what requested the reboot. That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well. Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* You can of course open a bug on bugzilla and attach there logs if you want. Thanks, and thanks for the report! -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] hosted-engine rebooting in the middle of setup (was: [vdsm] [ANN] oVirt 3.4.0 Release Candidate is now available)
Sounds like your hosts were not in maintenance mode while you were upgrading the engine which explains the 2 min reboot. This should be revealed by logs Regards Liviu On Sun, Mar 2, 2014 at 10:32 PM, Yedidyah Bar David d...@redhat.com wrote: - Original Message - From: Darrell Budic darrell.bu...@zenfire.com To: Sandro Bonazzola sbona...@redhat.com Cc: annou...@ovirt.org, engine-devel engine-de...@ovirt.org, arch a...@ovirt.org, Users@ovirt.org, VDSM Project Development vdsm-de...@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3. On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates. On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal. On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn't start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn't reveal what requested the reboot. That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well. Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* You can of course open a bug on bugzilla and attach there logs if you want. Thanks, and thanks for the report! -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users