diff options
| author | Wangpan <hzwangpan@corp.netease.com> | 2013-02-17 09:57:23 +0800 |
|---|---|---|
| committer | Wangpan <hzwangpan@corp.netease.com> | 2013-02-17 09:59:38 +0800 |
| commit | 27330ac85c4353d9124b8788c727e1ce40f55ea8 (patch) | |
| tree | 017f2f9c671daefdb48946b5b4eb2b2d581ed742 /tools/hacking.py | |
| parent | d49d504d23ebb6ae7d12e6aba37f66e7c3839ecf (diff) | |
| download | nova-27330ac85c4353d9124b8788c727e1ce40f55ea8.tar.gz nova-27330ac85c4353d9124b8788c727e1ce40f55ea8.tar.xz nova-27330ac85c4353d9124b8788c727e1ce40f55ea8.zip | |
Fix instance can not be deleted after soft reboot
The reason is 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.
So the domain id is checked during _wait_for_destroy loop, if it changed and
the instance is still running, we need to destroy it again.
If the domain is booted after _wait_for_destroy, it may result in
unfilter_instance failed because the nwfilter is in use, so doing the same
thing as above.
Fixes Bug #1111213
Change-Id: I98dc902dd86fa828f5821465c611953e08f9f637
Diffstat (limited to 'tools/hacking.py')
0 files changed, 0 insertions, 0 deletions