** Also affects: nova/juno
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/1429093
Title:
nova allows to boot images with virtual size > root_gb specified in
flavor
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) juno series:
New
Status in OpenStack Compute (nova) kilo series:
Fix Released
Status in OpenStack Security Advisory:
Won't Fix
Bug description:
It's currently possible to boot an instance from a QCOW2 image, which
has the virtual size larger than root_gb size specified in the given
flavor.
Steps to reproduce:
1. Download a QCOW2 image (e.g. Cirros -
https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-i386-disk.img)
2. Resize the image to a reasonable size:
qemu-img resize cirros-0.3.0-i386-disk.img +9G
3. Upload the image to Glance:
glance image-create --file cirros-0.3.0-i386-disk.img --name cirros-
10GB --is-public True --progress --container-format bare --disk-format
qcow2
4. Boot the first VM using a 'correct' flavor (root_gb > virtual size
of the Cirros image), e.g. m1.small (root_gb = 20)
nova boot --image cirros-10GB --flavor m1.small demo-ok
5. Wait until the VM boots.
6. Boot the second VM using an 'incorrect' flavor (root_gb < virtual
size of the Cirros image), e.g. m1.tiny (root_gb = 1):
nova boot --image cirros-10GB --flavor m1.tiny demo-should-fail
7. Wait until the VM boots.
Expected result:
demo-ok is in ACTIVE state
demo-should-fail is in ERROR state (failed with FlavorDiskTooSmall)
Actual result:
demo-ok is in ACTIVE state
demo-should-fail is in ACTIVE state
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1429093/+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
