Instance can not be deleted after soft reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
wangpan | ||
Folsom |
Won't Fix
|
High
|
Vish Ishaya |
Bug Description
Reproduce steps in devstack:
1. create an instance(a instance doesn't support acpi is better)
2. soft reboot it
3. wait a minute and delete it
this is a race condition issue, so it is probabilistic to reproduce it, but you can add a time.sleep(10) to nova/virt/
timer = utils.FixedInte
then the instance can not be deleted even when we delete it several times.
The reason may be that:
1. soft reboot will wait for instance become to 'shutdown', and then start it
2. delete operation also wait for this, and then clean up the instance
3. if soft reboot found the instance become to 'shutdown' firstly, it will start it immediately
4. then the delete operation will go to the _wait_for_destroy loop, and the loop may be endless
5. when we delete the instance again, because the lock was hold by the delete operation before, this one will wait the lock and don't implement actually.
Changed in nova: | |
assignee: | nobody → Matthew Sherborne (msherborne+openstack) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → High |
milestone: | none → grizzly-rc1 |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
Hi Matthew, I have already post a commit to fix this bug, /review. openstack. org/#/c/ 20883/2
https:/