soft_reboot followed by hard_reboot can lead to double reboot
Bug #1046356 reported by
Vish Ishaya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
wangpan | ||
Folsom |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
A change recently went in (https:/
Changed in nova: | |
assignee: | Yun Mao (yunmao) → wangpan (hzwangpan) |
status: | Triaged → In Progress |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
I can't think of a great way around this. The best short term fix I can come up with is to check to make sure the task state is still in SOFT_REBOOTING when the soft reboot fails. Not the best strategy for no_db_compute but probably workable.