[Bug 1369465] Re: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend

[Edward Hope-Morley]

Resubmitting sru as per above.

** Description changed:

  [Impact]
  
-  * Not able to resize rbd backed disk image.
+   Instance resize does not work if the target host has a cached copy of
+   the root disk. The resize will silently fail but be displayed as
+   successful in Nova.
  
  [Test Case]
  
- 1 - boot an instance with rbd backed disk image
- 2 - resize it
- 3 - log into the VM
- 4 - the disk is not enlarged without this patch
+   1 deploy nova-compute with RBDImageBackend enabled
+   2 boot an instance from a QCOW2 image (to guarantee it gets downloaded for reformat prior to re-upload to ceph)
+   3 nova resize using flavor with larger root disk
+   4 wait for instance resize migration to complete
+   5 verify root disk actually resized by checking /proc/partitions in vm
+   6 do nova resize-confirm
+   7 repeat steps 3-6
  
  [Regression Potential]
  
   * None
  
+ == original description below ==
  
  tested with nova trunk commit eb860c2f219b79e4f4c5984415ee433145197570
  
  Configured Nova to use rbd disk backend
  
  nova.conf
  
  [libvirt]
  images_type=rbd
  
  instances booted successfully and instance disks are in rbd pools, when
  perform a nova resize  to an existing instance,  memory and CPU changed
  to be new flavors but instance disks size doesn't change

** Summary changed:

- nova resize doesn't resize(extend) rbd disk files when using rbd disk backend
+ [sru] nova resize doesn't resize(extend) rbd disk files when using rbd disk backend

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1369465

Title:
  [SRU] nova resize doesn't resize(extend) rbd disk files when using rbd
  disk backend

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Triaged
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) liberty series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Wily:
  Triaged

Bug description:
  [Impact]

    Instance resize does not work if the target host has a cached copy of
    the root disk. The resize will silently fail but be displayed as
    successful in Nova.

  [Test Case]

    1 deploy nova-compute with RBDImageBackend enabled
    2 boot an instance from a QCOW2 image (to guarantee it gets downloaded for reformat prior to re-upload to ceph)
    3 nova resize using flavor with larger root disk
    4 wait for instance resize migration to complete
    5 verify root disk actually resized by checking /proc/partitions in vm
    6 do nova resize-confirm
    7 repeat steps 3-6

  [Regression Potential]

   * None

  == original description below ==

  tested with nova trunk commit eb860c2f219b79e4f4c5984415ee433145197570

  Configured Nova to use rbd disk backend

  nova.conf

  [libvirt]
  images_type=rbd

  instances booted successfully and instance disks are in rbd pools,
  when perform a nova resize  to an existing instance,  memory and CPU
  changed to be new flavors but instance disks size doesn't change

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1369465/+subscriptions