_validate_bdm not using the 'reserve_volume' Cinder API in a multi-cell environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
melanie witt | ||
Pike |
Fix Committed
|
Medium
|
Matt Riedemann |
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:/
I found this while working on improvements for the CellDatabases test fixture.
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: api volumes |
Changed in nova: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/539755
Review: https:/