From: "Uwe Laverenz" <uwe(a)laverenz.de&gt; To: users(a)ovirt.org Sent: Saturday, February 28, 2015 3:41:55 PM Subject: [ovirt-users] hosted-engine : how to shutdown hosts? Hi, just a minor problem I guess: I have a small test environment with 2 hosts and a hosted engine on a separate NFS3 share, all running CentOS7. The VMs are running from an iSCSI storage. When I want to shutdown the environment I: - shutdown VMs - enable global maintenance mode - "shutdown -h now" on the hosted engine vm - "shutdown -h now" on the hosts The problem: instead of shutting down, the hosts perform a reboot after a short while.

Is this the expected behaviour or a known bug? How can I cleanly shutdown my OVirt-environment?

On Sun, Mar 01, 2015 at 02:26:12AM -0500, Yedidyah Bar David wrote: > You wrote '"shutdown -h now" on the hosts'. What happens if you shutdown > just one of them and then wait a bit? Does it get started too? > > Are you certain that 'shutdown -h now' worked on these hosts before the > setup - that it's not some kernel/bios/etc issue? I've seen similar issues on some CentOS 7 hosts running on desktop-class hardware. I haven't got time for extensive debugging, but I'd bet it's a kernel or hardware-related issue (or a combination of both). There's nothing indicating that this is related to oVirt, at least in my case. Regards - Frank

From: "Frank Wall" <fw(a)moov.de&gt; To: users(a)ovirt.org Sent: Monday, June 22, 2015 11:41:02 AM Subject: Re: [ovirt-users] hosted-engine : how to shutdown hosts? On Mon, Mar 02, 2015 at 11:25:38AM +0100, Frank Wall wrote: > On Sun, Mar 01, 2015 at 02:26:12AM -0500, Yedidyah Bar David wrote: > > You wrote '"shutdown -h now" on the hosts'. What happens if you shutdown > > just one of them and then wait a bit? Does it get started too? > > > > Are you certain that 'shutdown -h now' worked on these hosts before the > > setup - that it's not some kernel/bios/etc issue? > > I've seen similar issues on some CentOS 7 hosts running on desktop-class > hardware. I haven't got time for extensive debugging, but I'd bet it's a > kernel or hardware-related issue (or a combination of both). There's > nothing indicating that this is related to oVirt, at least in my case. FWIW, after upgrading to CentOS 7.1.1503 (and oVirt 3.5.3) this issue is gone, at least for me.