Image name with boot from volume

[Aaron Mehar]

It does not seem possible to use an image name, when using block_device_mapping. The image ID, seems to work with no issue; The is using Rackspace

This works
------------------------------------------------------------------
          block_device_mapping_v2:
            - device_name: vda
              delete_on_termination: true
              image_id: d77b62e4-5f79-4e03-8dc1-925472901f6d
              volume_size: { get_param: nodesize }
------------------------------------------------------------------

and this does not
-------------------------------
          block_device_mapping_v2:
            - device_name: vda
              delete_on_termination: true
              image_id: CentOS 7 (PVHVM)
              volume_size: { get_param: nodesize }
------------------------------------------------------------------

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/298352

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/298352
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=120a1e7f0988da6acb0bf11ff09a501215772037
Submitter: Jenkins
Branch: master

commit 120a1e7f0988da6acb0bf11ff09a501215772037
Author: Dmitriy Uvarenkov <email address hidden>
Date: Tue Mar 29 18:15:55 2016 +0300

    Added new property 'image' for bdm_v2 in Nova Server

    Old property 'image_id' for bdm_v2 is now deprecated.

    Closes-Bug: #1559186
    Change-Id: I05cc8862b9dffbed113b333f1b8d3abe03612d13

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/heat 7.0.0.0b1 development milestone.

[Federico Iezzi (fiezzi)]

Hi there,

Is it possible to consider a back-port to Mitaka, Liberty and Kilo? It seems that this issue affects all of the OpenStack Heat releases since "block_device_mapping_v2" has been introduced.

Thanks