yahoo-eng-team team mailing list archive

[Jean Pierre Roquesalane <2002535@xxxxxxxxxxxxxxxxxx>]

I tried to reproduce the issue with the current code and I was unable to
do so.

All resize operations with devstack stable/master run fine, I'll abandon
this patch. Thanks for the update.

** Changed in: nova
       Status: New => Invalid

** Changed in: cinder
       Status: In Progress => 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/2002535

Title:
  [NFS] Server resize failed when using volume from image

Status in Cinder:
  Invalid
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description: When resizing an instance, an error is thrown to the
  user:

  Error resizing server: 17a238f3-01be-490c-97c8-35f47c804624
  Error resizing server

  Steps to reproduce: 
  1.  Create a bootable volume from an existing image
  openstack volume create --image cirros-0.5.2-x86_64-disk --size 1 --bootable volboot
  2.  Create an instance attached to that volume
  openstack server create --flavor m1.small --volume volboot --network public  server1
  3.  Resize the server
  openstack server resize --flavor m1.medium --wait server1

  In the nova compute logfile, we can see an error which refers to the disk format
  .
  Jan 10 20:29:09 e2e-os-pstorenfs105 nova-compute[3362105]: ERROR oslo_messaging.rpc.server libvirt.libvirtError: internal error: process exited while connecting to monitor: 2023-01-10T12:29:08.542757Z qemu-system-x86_64: -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":

  {"direct":true,"no-flush":false}

  ,"driver":"qcow2","file":"libvirt-1-storage","backing":null}: Image is
  not in qcow2 format

  
  After a first analysis, it seems that during the creation of the volume, qemu-img convert qcow2 file format to raw and never converts it back to qcow2. Attachement information then mistmatches and server resize is failing.

  It's an NFS environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/2002535/+subscriptions