Volume is not unreserved after scheduling is failed
Bug #1713641 reported by
Hironori Shiina
This bug report is a duplicate of:
Bug #1404867: Volume remains in-use status, if instance booted from volume is deleted in error state.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Medium
|
Chris Friesen | ||
Bug Description
For creating instance with booting from a volume, the volume is reserved before scheduling[1]. When the scheduling is failed due to lack of valid hosts, the instance gets in ERROR state and the volume is kept in 'attaching' state. The volume reservation is not removed even if the instance is deleted.
| summary: |
- Volume is not unreserved after schduling is failed + Volume is not unreserved after scheduling is failed |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: volumes |
| Changed in nova: | |
| assignee: | nobody → Li Xipeng (lixipeng) |
| tags: | added: pike-backport-potential |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| assignee: | Li Xipeng (lixipeng) → Chris Friesen (cbf123) |
| status: | Confirmed → In Progress |
Revision history for this message
| Chris Friesen (cbf123) wrote Re: [Bug 1713641] Re: Volume is not unreserved after scheduling is failed | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on nova (master) | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/