MOS 5.1 on Centos.
Cepsh is used as backed for all images,volimes instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_cross_az_attach=false ).
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability-zone=az1 --key-name key-name --block-device "source=image,id=imageid,dest=volume,size=15,bootindex=1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID.
Env:
MOS 5.1 on Centos. cross_az_ attach= false ).
Cepsh is used as backed for all images,volimes instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability- zone=az1 --key-name key-name --block-device "source= image,id= imageid, dest=volume, size=15, bootindex= 1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID.