unmanage operation overloads "deleting" state
Bug #1478959 reported by
Eric Harney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Eric Harney |
Bug Description
The following sequence of events doesn't look safe:
1. Issue a "cinder unmanage" command, which puts a volume in "deleting" state as it begins the unmanage process.
2. Cinder volume restarts due to failure
3. Upon resume, Cinder volume manager will detect the "deleting" state and now issue a delete volume request w/o the unmanage flag, which is more destructive than the admin intended and may cause accidental data loss.
Changed in cinder: | |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in cinder: | |
assignee: | nobody → Eric Harney (eharney) |
To post a comment you must log in.
Unassigning due to no activity.