1) have multiple clusters/ datacenters
2) Nova boot with volume, ex:
nova boot bdm1 --flavor 2 --image cirros-0.3.2-i386-disk --block-device-mapping sdb=c279ad39-f1f9-4861-9d00-2de8f6df7756::5
Issue wont be seen if the volume gets created in the compute cluster itself. If so, delete the VM and move the volume to a datastore where the cluster's host wont have access to. Try nova boot again.
steps to reproduce:
1) have multiple clusters/ datacenters 0.3.2-i386- disk --block- device- mapping sdb=c279ad39- f1f9-4861- 9d00-2de8f6df77 56::5
2) Nova boot with volume, ex:
nova boot bdm1 --flavor 2 --image cirros-
Issue wont be seen if the volume gets created in the compute cluster itself. If so, delete the VM and move the volume to a datastore where the cluster's host wont have access to. Try nova boot again.