Don't create block device mappings in the API cell
Otherwise 2 block_device_mapping entries will be created
in the API cell:
- the first one (created by the API cell) will have close to
no information about the volume (device_name and volume_id are NULL)
- the second one (bubbled up from the compute cell) will contain
all the volume information
The first entry confuses Nova when creating an image since
it won't be able to find the associated volume (NULL) in Cinder.
The compute cell should create it first and propagate it up
to the API cell.
Reviewed: https:/ /review. openstack. org/152257 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=58633c4f085 fc21be1e6439bb3 d60d7492358d4a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 58633c4f085fc21 be1e6439bb3d60d 7492358d4a
Author: Mathieu Gagné <email address hidden>
Date: Mon Feb 2 14:22:24 2015 -0500
Don't create block device mappings in the API cell
Otherwise 2 block_device_ mapping entries will be created
in the API cell:
- the first one (created by the API cell) will have close to
no information about the volume (device_name and volume_id are NULL)
- the second one (bubbled up from the compute cell) will contain
all the volume information
The first entry confuses Nova when creating an image since
it won't be able to find the associated volume (NULL) in Cinder.
The compute cell should create it first and propagate it up
to the API cell.
Change-Id: I38edb953e73de6 bc70a2e5950c68f 457f83303e1
Closes-bug: #1417239