Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/horizon-block-device-mapping-v2. Description: Right now, when booting from a volume, horizon uses a different block_device_mapping depending on the source: v1 if the source is a volume or an snapshot and v2 if it is an image. https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L571 The "create instance" menu should check if BMDv2 extension is enabled in the server side. If that is the case, booting from a volume, a volume created from a snapshot or an image should be enabled and using the BDMv2 API call. If only BDMv1 is enabled in the server, booting an instance from a volume created from an image shouldn't be allowed. All the other options would use the BDMv2 API call. In the case where none of the extensions is enabled, it shouldn't be allowed to boot from a volume at all. Specification URL (additional information): None
Verified on: python-django-horizon-8.0.1-1.el7ost.noarch ======================================================== 1. Sanity test - Pass 2. Booting from Volume - Pass Booting from image (create new volume) - Pass Booting from volume snapshot (create new volume) - Pass Note: All extensions are enabled by default, can't configure which version to use (BMDv1 or BMDv2)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0603.html