Instance vm_state remains 'migrating' if source compute node goes down during migration
Bug #973393 reported by
Unmesh Gurjar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Jian Wen |
Bug Description
Scenario: During live migration of an instance, if the source Compute node goes down, the instance vm_state remains set to 'migrating'.
Expected Behavior: The instance state must be updated to vm_state to 'error'.
Actual Behavior: Instance remains in following state vm_state=migrating, task_state=NULL, power_state=1
Such instances should be monitored and the vm_state must be updated to 'error'. Because until the source compute server comes up, no actions can be performed on the instance.
Changed in nova: | |
assignee: | nobody → Unmesh Gurjar (unmesh-gurjar) |
Changed in nova: | |
assignee: | nobody → Jian Wen (wenjianhn) |
status: | Incomplete → Confirmed |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
no longer affects: | nova/folsom |
To post a comment you must log in.
Which version did you see that with ? Any chance you could check with current Folsom ?