OpenStack Compute (nova)

Volume is not unreserved after creating is failed

Bug #1734066 reported by Li Xipeng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Undecided
Li Xipeng

Bug Description

For creating instance with booting from a volume, the volume is reserved when before schedule and build in nova compute. When block-device-mapping failed due to cinder volume busy or other reason, 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.

This bug seems like bug https://bugs.launchpad.net/nova/+bug/1713641。

Li Xipeng (lixipeng)
Changed in nova:
status: New → In Progress
assignee: nobody → Li Xipeng (lixipeng)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/522486

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/522486
Reason: This was fixed in I8b1c05317734e14ea73dc868941351bb31210bf0.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.