Nova doesn't support resize operation for instance booted from volume

Bug #1240011 reported by Yaguang Tang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Nova doesn't support resize operation for instance booted from any volume backend.

Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

I think this one was fixed in https://bugs.launchpad.net/nova/+bug/1241337

Changed in nova:
assignee: nobody → Jay Lau (jay-lau-513)
Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

Yaguang, can you please append some stack trace for the issue? Does the error caused by rpc related to context? Thanks.

Revision history for this message
Yaguang Tang (heut2008) wrote :

from the current implementation of resize of libvirt. when instance flavor is changed, we use qemu-img to change the instance disk size. so it's obvious that instance booted from volume cann't be resized , there is no volume API to extend existed volume also.

Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :

Thanks Yaguang. In my understanding, now resize should only care vcpu/memory but not disk, can you please append some command line and their output related to this bug?

Revision history for this message
Matt Riedemann (mriedem) wrote :

Need some recreate steps and logs of exception stack traces in a paste to pursue this.

tags: added: libvirt volumes
Changed in nova:
status: New → Incomplete
Sean Dague (sdague)
Changed in nova:
assignee: Jay Lau (jay-lau-513) → nobody
Sean Dague (sdague)
Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.