Volume is not unreserved after creating is failed
Bug #1734066 reported by
Li Xipeng
This bug report is a duplicate of:
Bug #1633249: Boot volume creation failure leaves secondary volume attached to broken server.
Edit
Remove
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-
This bug seems like bug https:/
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → Li Xipeng (lixipeng) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/522486
Review: https:/