[openstack-dev] Adding a clean shutdown for stop/delete breaks Jenkins

Day, Phil philip.day at hp.com
Wed Jul 3 16:30:55 UTC 2013

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130703/4ed044e1/attachment.html>

More information about the OpenStack-dev mailing list