yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32413
[Bug 1449084] [NEW] Boot from volume does not boot from volume
Public bug reported:
Booting from volume does not actually boot from the volume; it boots
from a Glance image. Perform the following steps to test this:
Using the GUI steps:
1. In the "Volumes" tab, select "Create Volume". For "Volume Source", select an image (I use CirrOS). Click "Create Volume".
2. On your host machine, open a terminal and overwrite the volume:
$ sudo dd if=/dev/zero of=dev/stack-volumes-lvmdriver-1/volume-[ID OF VOLUME] bs=10M
3. In the "Instances" tab, select "Launch Instance". For "Instance Boot Source", select "Boot from volume". Be sure to select a flavor with enough storage to support the volume (if using CirrOS, pick m1.tiny). For "Volume", select the volume you created in step 1. Click "Launch".
Using the CLI:
1. Create the volume:
cinder create --image-id $(glance image-list | grep cirros-0.3.1-x86_64-uec[^-] | cut -d '|' -f 2 | xargs echo) --name sample-volume 1
2. Overwrite the volume:
$ sudo dd if=/dev/zero of=dev/stack-volumes-lvmdriver-1/volume-[ID OF VOLUME] bs=10M
3. Boot the volume:
nova boot --flavor m1.tiny --boot-volume sample-volume instance
Expected result: The instance should not boot in either of these cases; the volumes are empty.
Actual result: The instance boots successfully in both of these cases.
Additional test to show that the instance is actually being booted from
the Glance image:
Using the CLI:
1. Create the volume:
cinder create --image-id $(glance image-list | grep cirros-0.3.1-x86_64-uec[^-] | cut -d '|' -f 2 | xargs echo) --name sample-volume 1
2. Delete the Glance image:
glance image-list | grep cirros-0.3.1-x86_64-uec | cut -d '|' -f 2 | xargs glance image-delete
3. Attempt to boot the volume:
nova boot --flavor m1.tiny --boot-volume sample-volume instance
Expected result: This should succeed; we are attempting to boot from the volume.
Actual result: This fails.
** Affects: nova
Importance: Undecided
Status: New
--
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/1449084
Title:
Boot from volume does not boot from volume
Status in OpenStack Compute (Nova):
New
Bug description:
Booting from volume does not actually boot from the volume; it boots
from a Glance image. Perform the following steps to test this:
Using the GUI steps:
1. In the "Volumes" tab, select "Create Volume". For "Volume Source", select an image (I use CirrOS). Click "Create Volume".
2. On your host machine, open a terminal and overwrite the volume:
$ sudo dd if=/dev/zero of=dev/stack-volumes-lvmdriver-1/volume-[ID OF VOLUME] bs=10M
3. In the "Instances" tab, select "Launch Instance". For "Instance Boot Source", select "Boot from volume". Be sure to select a flavor with enough storage to support the volume (if using CirrOS, pick m1.tiny). For "Volume", select the volume you created in step 1. Click "Launch".
Using the CLI:
1. Create the volume:
cinder create --image-id $(glance image-list | grep cirros-0.3.1-x86_64-uec[^-] | cut -d '|' -f 2 | xargs echo) --name sample-volume 1
2. Overwrite the volume:
$ sudo dd if=/dev/zero of=dev/stack-volumes-lvmdriver-1/volume-[ID OF VOLUME] bs=10M
3. Boot the volume:
nova boot --flavor m1.tiny --boot-volume sample-volume instance
Expected result: The instance should not boot in either of these cases; the volumes are empty.
Actual result: The instance boots successfully in both of these cases.
Additional test to show that the instance is actually being booted
from the Glance image:
Using the CLI:
1. Create the volume:
cinder create --image-id $(glance image-list | grep cirros-0.3.1-x86_64-uec[^-] | cut -d '|' -f 2 | xargs echo) --name sample-volume 1
2. Delete the Glance image:
glance image-list | grep cirros-0.3.1-x86_64-uec | cut -d '|' -f 2 | xargs glance image-delete
3. Attempt to boot the volume:
nova boot --flavor m1.tiny --boot-volume sample-volume instance
Expected result: This should succeed; we are attempting to boot from the volume.
Actual result: This fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1449084/+subscriptions
Follow ups
References