This issue has been fixed by https://review.openstack.org/#/c/33296/.
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1155512
Title:
Issues with booting from the volume
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Folks, correct me when I make a mistake.
Issue 1:
First, I create a bootable volume with "cinder create --image-id
$image_id--display_name=boot_volume --display_description "test bootable
volume" 2".
What I expect: the image has been copied into the volume.
Then, I boot a VM from this volume with "nova boot --flavor 2
--block-device-mapping vda=$vol_id --security_groups=default VM_test".
What I expect: the VM should be successfully booted and in healthy state.
Result: The VM is unable to ping.
Issue 2:
First, I create a volume with with "cinder create 2".
Then, I boot a VM from this non-bootable volume with "nova boot --flavor 2
--block-device-mapping vda=$vol_id --security_groups=default VM_test_1".
What I expect: see some warning or error message telling me that this volume
is not bootable.
Result: the VM is successfully booted with no error, but it cannot be pinged.
Please advise with your comments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1155512/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
