ec2 instance does not shut down after test failures
Bug #617598 reported by
Māris Fogels
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Māris Fogels |
Bug Description
EC2 instances started by 'ec2 land' are not shutting down after the test suite has finished.
The server does send the final email. The server does correctly exit the 'make check' step.
Here is the tail of the test log from a server that shut down successfully after a test suite failure: http://
See this thread on the launchpad-dev mailing list for more information: https:/
Related branches
lp:~mars/launchpad/fix-ec2-shutdown-617598
- Guilherme Salgado (community): Approve
-
Diff: 36 lines (+13/-2)2 files modifiedlib/devscripts/ec2test/builtins.py (+1/-1)
lib/devscripts/ec2test/testrunner.py (+12/-1)
Changed in launchpad-foundations: | |
status: | Triaged → In Progress |
Changed in launchpad-foundations: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
You can't run two shutdown calls at the same time.
The remote.py script in ec2 test call 'sudo shutdown -P now' when the test suite has finished. However, we already put a shutdown in place as an earlier 8-hour failsafe. The failsafe shutdown blocks the end-of-suite shutdown from happening. Thus the server stays alive for the full test run.
Evidence:
ec2test@ domU-12- 31-39-0E- 62-61:~ $ sudo shutdown -P now domU-12- 31-39-0E- 62-61:~ $
shutdown: Another shutdown is already running
ec2test@
To solve this I can cancel the existing shutdown with 'shutdown -c', then call it again with '-P now'.