providing different imageRef when using block_device_mapping (image -> volume)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
When booting instance with block_device_
Steps to reproduce
==================
Step 1:
=======
call /servers api curl REQ:
curl -g -i -X POST http://
Step 2:
=======
check server information: openstack server show 5e903f37-
+------
| Field | Value |
+------
| image | Image1 (cbb2746c-
| name | new-server-test |
| os-extended-
+------
Step 3:
=======
check volume information: openstack volume show e03eb79c-
+------
| Field | Value |
+------
| volume_
| | u'1616a9c4-
+------
Expected Result
===============
server should not be tagged with image image1 since the actual image source is the image2 specified in block_device_
Actual Result
==============
server is tagged with image image1
Changed in nova: | |
assignee: | nobody → Nazeema Begum (nazeema123) |
Changed in nova: | |
status: | Confirmed → In Progress |
Should Nova API validate that when specifying both imageRef and block_device_ mapping_ v2 with source image that both images be the same?