Ghosing volumes after delete
Bug #1245577 reported by
Denis M.
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Expired
|
Low
|
Unassigned | ||
Bug Description
When deleting trove instance with status ERROR casued by nova server (nova server status is ERROR) volume stays not attached to any of instances
| Changed in trove: | |
| status: | New → Confirmed |
Revision history for this message
| Nikhil Manchanda (slicknik) wrote | #1 |
| Changed in trove: | |
| status: | Confirmed → Incomplete |
| Changed in trove: | |
| importance: | Undecided → Low |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in trove: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Can you please put more information in the bug? I'm not sure what the bug here is.
Thanks!