When cross_az_attach set to false and creating VM with bootable volumes created before, InvalidBDM error raised.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
John Haan |
Bug Description
Description
===========
When cross_az_attach option is set to False and you try to boot an instance with bootable volume created before, InvalidBDM error raised.
Steps to reproduce
==================
1. Configure multiple AZs in Nova and Cinder.
- for Nova : AZ1 and AZ2
- for Cinder : AZ1 and AZ2
2. cross_az_attach set to false in nova.conf
[cinder]
cross_az_attach = False
3. Restart nova-compute service
4. Create volume from glance image
$ cinder create 10 --display-name test-bootable-
5. Create instance from the volume created
$ nova boot --flavor m1.small --boot-volume 7c15ae47-
Expected result
===============
Instance is booted successfully in AZ1 zone.
Actual result
=============
Instance failed to boot and raise InvalidBDM Error
nova command output says:
ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume 7c15ae47-
nova-api.log says:
2016-12-02 20:02:48.724 150051 DEBUG cinderclient.client [req-8356085e-
2016-12-02 20:02:48.734 150051 DEBUG nova.quota [req-8356085e-
2016-12-02 20:02:48.734 150051 INFO nova.api.
2016-12-02 20:02:48.735 150051 DEBUG nova.api.
2016-12-02 20:02:48.736 150051 INFO nova.osapi_
Environment
===========
Ubuntu 16.04, qemu, Cinder ceph
Nova version: stable/newton
Two AZs configured in Nova and Cinder
Changed in nova: | |
assignee: | nobody → John Haan (yongiman) |
Fix proposed to branch: master /review. openstack. org/409680
Review: https:/