[openstack-dev] Adding a clean shutdown for stop/delete breaks Jenkins
dkranz at redhat.com
Wed Jul 3 17:08:04 UTC 2013
On 07/03/2013 12:30 PM, Day, Phil wrote:
> Hi Folks,
> I have a change submitted which adds the same clean shutdown logic to
> stop and delete that exists for soft reboot -- the rational being that
> its always better to give a VM a chance to shutdown cleanly if
> possible even if you're about to delete it as sometimes other parts of
> the application expect this, and if its booted from a volume you want
> to leave the guest file system in a tidy state.
> However setting the default value to 120 seconds (as per soft reboot)
> causes the Jenkins gate jobs to blow the 3 hour limit. This seems to
> be just a gradual accumulation of extra time rather than any one test
> running much longer.
> So options would seem to be:
> i)Make the default wait time much shorter so that Jenkins runs OK
> (tries this with 10 seconds and it works fine), and assume that users
> will configure it to a more realistic value.
> ii)Keep the default at 120 seconds, but make the Jenkins jobs use a
> specific configuration setting (is this possible, and iof so can
> someone point me at where to make the change) ?
> iii)Increase the time allowed for Jenkins
> iv)The ever popular something else ...
> Thought please.
The fact that changing the timeout changes gate time means the code is
actually hitting the timeout. Is that expected?
Shutdown is now relying on the guest responding to acpi. Is that what we
want? Tempest uses a specialized image and I'm not sure how it is set up
in this regard. In any event I don't think we want to add any more time
to server delete when running in the gate.
I'm also a little concerned that this seems to be a significant behavior
change when using vms that behave like the ones in the gate. In reboot
this is handled by having soft/hard options of course.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev