yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #70908
[Bug 1746634] Re: _validate_bdm not using the 'reserve_volume' Cinder API in a multi-cell environment
** Changed in: nova
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/1746634
Title:
_validate_bdm not using the 'reserve_volume' Cinder API in a multi-
cell environment
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) pike series:
In Progress
Bug description:
During instance creation, we call _validate_bdm to valid block device
mappings boot indexes, accessibility, attachability, etc and we call
the Cinder API to do some of that. We query the service version to
decide which Cinder APIs to call and currently, we aren't querying all
cells for the service version. Because we're creating an instance, we
don't yet know what cell it will land in, so we must query all cells
to correctly get the service version. Else, we get a service version
of 0 and we'll use the old 'check_attach' Cinder API instead of the
newer 'reserve_volume' API in a multi-cell environment.
https://github.com/openstack/nova/blob/c1442d3/nova/compute/api.py#L1326
I found this while working on improvements for the CellDatabases test
fixture.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1746634/+subscriptions
References