I have run into a scenario after installing the client agent. If a VM is shutdown, the client agent calls the shutdown command with a 1 minute timeout. Dummy-2::INFO::2013-03-28 14:05:21,892::vdsAgentLogic::138::root::Shutting down (timeout = 30, message = 'System Administrator has initiated shutdown of this Virtual Machine. Virtual Machine is shutting down.' Since the shutdown command is called with time parameter the VM sets the /etc/nologin file. When the VM is forced down the /etc/nologin file is not cleared and when it comes back up only root can login until the /etc/nologin file is cleared.

Is their some some reason the shutdown time is set to 30 seconds (rounded up to 1 minute in the code)? Are there any know issues with setting this to 0?

Is this the right way to change it to 0? psql engine postgres -c "update vdc_options set option_value = '0' where option_name = 'VmGracefulShutdownTimeout';" _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 20 Apr 2013, at 22:42, Itamar Heim <iheim(a)redhat.com&gt; wrote: > On 03/29/2013 04:58 AM, Thomas Scofield wrote: >> I have run into a scenario after installing the client agent. If a VM >> is shutdown, the client agent calls the shutdown command with a 1 minute >> timeout. >> >> Dummy-2::INFO::2013-03-28 >> 14:05:21,892::vdsAgentLogic::138::root::Shutting down (timeout = 30, >> message = 'System Administrator has initiated shutdown of this Virtual >> Machine. Virtual Machine is shutting down.' >> >> Since the shutdown command is called with time parameter the VM sets the >> /etc/nologin file. When the VM is forced down the /etc/nologin file is >> not cleared and when it comes back up only root can login until the >> /etc/nologin file is cleared. > hmmm, Vinzenz - should guest agent clear that on guest startup, if guest agent set this at shutdown? It's not guest agent, "shutdown" does it. It behaves the same on real hw >> Is their some some reason the shutdown time is set to 30 seconds >> (rounded up to 1 minute in the code)? Are there any know issues with >> setting this to 0? > Vinzenz - if we are rounding up - is this a bug? possibly yes

>> Is this the right way to change it to 0? >> psql engine postgres -c "update vdc_options set option_value = '0' where >> option_name = 'VmGracefulShutdownTimeout';" notmally the grace period is there for other users to react befor shutdown starts. I wonder if it's that much relevant here.., if we assume single user most of the time 0 (i.e. "now") should be ok >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >>

From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com&gt; To: users(a)ovirt.org, "Thomas Scofield" <tscofield(a)gmail.com&gt;, "Vinzenz Feenstra" <vfeenstr(a)redhat.com&gt;, "Barak Azulay" <bazulay(a)redhat.com&gt;, "Gal Hammer" <ghammer(a)redhat.com&gt; Sent: Monday, April 22, 2013 11:48:18 AM Subject: Re: [Users] forced shutdown with client agent On Apr 20, 2013, at 22:42 , Itamar Heim <iheim(a)redhat.com&gt; wrote: > On 03/29/2013 04:58 AM, Thomas Scofield wrote: >> I have run into a scenario after installing the client agent. If >> a VM >> is shutdown, the client agent calls the shutdown command with a 1 >> minute >> timeout. >> >> Dummy-2::INFO::2013-03-28 >> 14:05:21,892::vdsAgentLogic::138::root::Shutting down (timeout = >> 30, >> message = 'System Administrator has initiated shutdown of this >> Virtual >> Machine. Virtual Machine is shutting down.' >> >> Since the shutdown command is called with time parameter the VM >> sets the >> /etc/nologin file. When the VM is forced down the /etc/nologin >> file is >> not cleared and when it comes back up only root can login until >> the >> /etc/nologin file is cleared. > > hmmm, Vinzenz - should guest agent clear that on guest startup, if > guest agent set this at shutdown? > >> >> Is their some some reason the shutdown time is set to 30 seconds >> (rounded up to 1 minute in the code)? Are there any know issues >> with >> setting this to 0? I wouldn't mind changing this to 0 by default if there are no objections. Barak, Gal, what do you think? Do you see any strong reason for keeping a grace period?

> > Vinzenz - if we are rounding up - is this a bug? > >> >> Is this the right way to change it to 0? >> psql engine postgres -c "update vdc_options set option_value = '0' >> where >> option_name = 'VmGracefulShutdownTimeout';" >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

> The idea was to allow a logged in user to orderly close his work right? > For that I'm not sure that even 30 seconds is enough. For that typically sysadmins use 5 or 10 minutes. 30s is worthless, no one would be able to react that fast…so to me this is the same as initiating shutdown right away. It's graceful anyway and all common apps would save the workspace on SIGTERM anyway. Well, does it even do anything on Windows? That's why I'd vote for 0. And keep is configurable in case you want to use it, sure.

From: "Itamar Heim" <iheim(a)redhat.com&gt; To: "Michal Skrivanek" <michal.skrivanek(a)redhat.com&gt; Cc: "Gal Hammer" <ghammer(a)redhat.com&gt;, users(a)ovirt.org, "Simon Grinberg" <sgrinber(a)redhat.com&gt; Sent: Tuesday, April 23, 2013 12:19:25 AM Subject: Re: [Users] forced shutdown with client agent On 04/22/2013 01:59 PM, Michal Skrivanek wrote: >> > >> >----- Original Message ----- >>> >>From: "Michal Skrivanek&quot;&lt;michal.skrivanek(a)redhat.com&gt; >>> >>To:users@ovirt.org, "Thomas Scofield&quot;&lt;tscofield(a)gmail.com&gt;, "Vinzenz >>> &gt;&gt;Feenstra&quot;&lt;vfeenstr(a)redhat.com&gt;, "Barak >>> &gt;&gt;Azulay&quot;&lt;bazulay(a)redhat.com&gt;, "Gal Hammer&quot;&lt;ghammer(a)redhat.com&gt; >>> >>Sent: Monday, April 22, 2013 11:48:18 AM >>> >>Subject: Re: [Users] forced shutdown with client agent >>> >> >>> >> >>> >>On Apr 20, 2013, at 22:42 , Itamar Heim&lt;iheim(a)redhat.com&gt; wrote: >>> >> >>>> >>>On 03/29/2013 04:58 AM, Thomas Scofield wrote: >>>>> >>>>I have run into a scenario after installing the client agent. If >>>>> >>>>a VM >>>>> >>>>is shutdown, the client agent calls the shutdown command with a 1 >>>>> >>>>minute >>>>> >>>>timeout. >>>>> >>>> >>>>> >>>>Dummy-2::INFO::2013-03-28 >>>>> >>>>14:05:21,892::vdsAgentLogic::138::root::Shutting down (timeout = >>>>> >>>>30, >>>>> >>>>message = 'System Administrator has initiated shutdown of this >>>>> >>>>Virtual >>>>> >>>>Machine. Virtual Machine is shutting down.' >>>>> >>>> >>>>> >>>>Since the shutdown command is called with time parameter the VM >>>>> >>>>sets the >>>>> >>>>/etc/nologin file. When the VM is forced down the /etc/nologin >>>>> >>>>file is >>>>> >>>>not cleared and when it comes back up only root can login until >>>>> >>>>the >>>>> >>>>/etc/nologin file is cleared. >>>> >>> >>>> >>>hmmm, Vinzenz - should guest agent clear that on guest startup, if >>>> >>>guest agent set this at shutdown? >>>> >>> >>>>> >>>> >>>>> >>>>Is their some some reason the shutdown time is set to 30 seconds >>>>> >>>>(rounded up to 1 minute in the code)? Are there any know issues >>>>> >>>>with >>>>> >>>>setting this to 0? >>> >>I wouldn't mind changing this to 0 by default if there are no >>> >>objections. >>> >>Barak, Gal, what do you think? Do you see any strong reason for >>> >>keeping a grace period? >> > >> >The idea was to allow a logged in user to orderly close his work right? >> >For that I'm not sure that even 30 seconds is enough. > For that typically sysadmins use 5 or 10 minutes. 30s is worthless, no one > would be able to react that fast…so to me this is the same as initiating > shutdown right away. It's graceful anyway and all common apps would save > the workspace on SIGTERM anyway. Well, does it even do anything on > Windows?

> That's why I'd vote for 0. And keep is configurable in case you want to use > it, sure. > do we allow users to cancel the shutdown?

_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com&gt; To: "Itamar Heim" <iheim(a)redhat.com&gt;, users(a)ovirt.org Cc: "Gal Hammer" <ghammer(a)redhat.com&gt;, "Simon Grinberg" <sgrinber(a)redhat.com&gt; Sent: Tuesday, April 23, 2013 9:58:57 AM Subject: Re: [Users] forced shutdown with client agent On Apr 22, 2013, at 23:19 , Itamar Heim <iheim(a)redhat.com&gt; wrote: > On 04/22/2013 01:59 PM, Michal Skrivanek wrote: >>> > >>> >----- Original Message ----- >>>> >>From: "Michal Skrivanek&quot;&lt;michal.skrivanek(a)redhat.com&gt; >>>> >>To:users@ovirt.org, "Thomas Scofield&quot;&lt;tscofield(a)gmail.com&gt;, >>>> >>"Vinzenz Feenstra&quot;&lt;vfeenstr(a)redhat.com&gt;, "Barak >>>> &gt;&gt;Azulay&quot;&lt;bazulay(a)redhat.com&gt;, "Gal Hammer&quot;&lt;ghammer(a)redhat.com&gt; >>>> >>Sent: Monday, April 22, 2013 11:48:18 AM >>>> >>Subject: Re: [Users] forced shutdown with client agent >>>> >> >>>> >> >>>> >>On Apr 20, 2013, at 22:42 , Itamar Heim&lt;iheim(a)redhat.com&gt; >>>> >> wrote: >>>> >> >>>>> >>>On 03/29/2013 04:58 AM, Thomas Scofield wrote: >>>>>> >>>>I have run into a scenario after installing the client >>>>>> >>>>agent. If >>>>>> >>>>a VM >>>>>> >>>>is shutdown, the client agent calls the shutdown command >>>>>> >>>>with a 1 >>>>>> >>>>minute >>>>>> >>>>timeout. >>>>>> >>>> >>>>>> >>>>Dummy-2::INFO::2013-03-28 >>>>>> >>>>14:05:21,892::vdsAgentLogic::138::root::Shutting down >>>>>> >>>>(timeout = >>>>>> >>>>30, >>>>>> >>>>message = 'System Administrator has initiated shutdown of >>>>>> >>>>this >>>>>> >>>>Virtual >>>>>> >>>>Machine. Virtual Machine is shutting down.' >>>>>> >>>> >>>>>> >>>>Since the shutdown command is called with time parameter >>>>>> >>>>the VM >>>>>> >>>>sets the >>>>>> >>>>/etc/nologin file. When the VM is forced down the >>>>>> >>>>/etc/nologin >>>>>> >>>>file is >>>>>> >>>>not cleared and when it comes back up only root can login >>>>>> >>>>until >>>>>> >>>>the >>>>>> >>>>/etc/nologin file is cleared. If you don't want it setting user_shutdown_timeout to 0 should solve this. >>>>> >>> >>>>> >>>hmmm, Vinzenz - should guest agent clear that on guest >>>>> >>>startup, if >>>>> >>>guest agent set this at shutdown? >>>>> >>> >>>>>> >>>> >>>>>> >>>>Is their some some reason the shutdown time is set to 30 >>>>>> >>>>seconds >>>>>> >>>>(rounded up to 1 minute in the code)? it is rounded up because unix shutdown works with minutes only. So it's the seconds from user_shutdown_timeout is rounded up to minutes. The Windows one should really be 30s. >>>>>> Are there any know issues >>>>>> >>>>with >>>>>> >>>>setting this to 0? >>>> >>I wouldn't mind changing this to 0 by default if there are no >>>> >>objections. >>>> >>Barak, Gal, what do you think? Do you see any strong reason >>>> >>for >>>> >>keeping a grace period? >>> > >>> >The idea was to allow a logged in user to orderly close his work >>> >right? >>> >For that I'm not sure that even 30 seconds is enough. >> For that typically sysadmins use 5 or 10 minutes. 30s is >> worthless, no one would be able to react that fast…so to me this >> is the same as initiating shutdown right away. It's graceful >> anyway and all common apps would save the workspace on SIGTERM >> anyway. Well, does it even do anything on Windows? >> That's why I'd vote for 0. And keep is configurable in case you >> want to use it, sure. >> > > do we allow users to cancel the shutdown? nope. It can be stopped inside the guest, well, if you manage to do that in that short time.

From all the said above seems that indeed default shut-down time should be 0

_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users