Marking this as invalid, as I think this is the correct behaviour.
There was talk of adding the ability to resize a volume during resize
using BDM, but thats a spec.
** Changed in: nova
Status: Confirmed => Invalid
--
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/1412993
Title:
Nova resize for boot-from-volume instance does not resize volume
Status in OpenStack Compute (nova):
Invalid
Bug description:
Resizing an instance which booted from a volume to a new flavor with a
bigger disk will not cause the volume to resize accordingly. This can
cause confusion among the users, which will expect to have instances
with bigger storage.
Scenario:
1. Have a glance image.
2. Create a bootable volume from glance image.
3. Create instance using volume and flavor having 10GB disk.
4. Perform nova resize on instance to a new flavor having 20GB disk.
5. After resize, see that the instance still has 10GB storage. Cinder volume
still has the same size.
This issue has been discussed on #openstack-nova and it was agreed
upon to fail the resize operation, if the given instance is booted
from volume and the given new flavor has a different disk size.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1412993/+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
