The issue was fixed in python-novaclient 7.0.0.
** Changed in: python-novaclient
Status: In Progress => Fix Released
--
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/
It does feel like it might be better to fix this on the client side.
Marking as opinion as the patch author abandoned the nova patch. It is
welcome to come back later.
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engin
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Changed in: python-openstackclient
Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)
** No longer affects: python-openstackclient
--
You received this bug notification because you are a member of Yaho
** Description changed:
- TBD
+ When booting instance with block_device_mapping provided, in the current
+ implementation, the "destination_type" is allowed to be None, and this
+ lead to un-sync between Nova and Cinder:
+
+ Step 1: Booting with block_device_mapping, leave destination_type to be
But Destination_type in bdm is optional, checks in nova will make it
backward incompatible. I am not sure why cinder does not mark volume in-
use.
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineer
5 matches
Mail list logo
