2015-08-15 10:12:48 |
Feodor Tersin |
description |
Since that https://review.openstack.org/#/c/182994/ is merged, Cinder doesn't allow an empty volume name. But Nova specifies it for a new volume when the volume is created from a snapshot or a volume. Thus boot operation fails on compute node.
Steps to reproduce:
1 Boot an instance from a volume which should be autocreated from an image
nova boot inst --block-device source=image,dest=volume,bootindex=0,size=1,id=<cirros_id> --flavor m1.nano
2 Wait a few time and look at the instance state
nova show inst
Expected result: the instance state is active.
Actual result: the instance state is error, current stage is block device mapping. |
Since that https://review.openstack.org/#/c/182994/ is merged, Cinder doesn't allow an empty volume name. But Nova specifies it for a new volume when the volume is created from a snapshot or a volume. Thus boot operation fails on compute node.
Steps to reproduce:
1 Boot an instance from a volume which should be autocreated from an image
nova boot inst --block-device source=image,dest=volume,bootindex=0,size=1,id=<cirros_id> --flavor m1.nano
2 Wait a bit and look at the instance state
nova show inst
Expected result: the instance state is active.
Actual result: the instance state is error, current stage is block device mapping. |
|