*** This bug is a duplicate of bug 1633249 ***
https://bugs.launchpad.net/bugs/1633249
** This bug has been marked a duplicate of bug 1633249
Boot volume creation failure leaves secondary volume attached to broken
server
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1734066
Title:
Volume is not unreserved after creating is failed
Status in OpenStack Compute (nova):
In Progress
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。
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1734066/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
