Reset state doesn't update migration status
Bug #1308253 reported by
John Griffith
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith | ||
python-cinderclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In the case of a failed migration the volume's status and the migration status are both set to error state. We have the ability to use reset-state to get the volume back to a usable state, however the migration-status isn't updated which makes it impossible to do things like delete the volume or perhaps retry the migration.
We should have the reset-state command clean up outliers like this as well.
Changed in cinder: | |
importance: | Undecided → Critical |
importance: | Critical → High |
assignee: | nobody → John Griffith (john-griffith) |
status: | New → Triaged |
Changed in python-cinderclient: | |
assignee: | Lingxian Kong (kong) → Jay Bryant (jsbryant) |
Changed in python-cinderclient: | |
assignee: | Jay Bryant (jsbryant) → Lingxian Kong (kong) |
Changed in cinder: | |
milestone: | none → juno-2 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in python-cinderclient: | |
assignee: | Lingxian Kong (kong) → nobody |
assignee: | nobody → hzxiongwenwu (xwwzzy) |
Changed in cinder: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/88083
Review: https:/