Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest

Tobias Urdin tobias.urdin at binero.com
Wed Feb 17 08:43:43 UTC 2021


Hello,


This adds support for Horizon https://review.opendev.org/c/openstack/horizon/+/749013


Regarding the actual extending of in-use volumes, we had an issue where cinder could not talk to os-server-external-events endpoint for nova because it used the wrong endpoint when looking up in keystone. We saw the error in cinder-volume.log except for that I can't remember we did anything special.


Had to use newer microversion for cinder when using CLI.

cinder --os-volume-api-version 3.42 extend <volume ID or name> <new size in GB>


Best regards

________________________________
From: Sean Mooney <smooney at redhat.com>
Sent: Wednesday, February 17, 2021 4:11:45 AM
To: openstack-discuss at lists.openstack.org
Subject: Re: Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest

On Tue, 2021-02-16 at 22:32 +0100, Christian Rohmann wrote:
> Hello Lee,
>
> thanks for quick response and sorry about the late reaction from my side.
>
>
>
> On 15/02/2021 12:18, Lee Yarwood wrote:
> > On 15-02-21 00:52:52, Christian Rohmann wrote:
> > > So I was simply wondering if this is expected to be working?
> > > Are there any special settings / options I need to set to enable this
> > > feature?
> > Yes this should work without any additonal changes, can you write up
> > a nova bug with the following output in addition to the bug template:
> >
> > - Your versions of libvirt and QEMU.
> >
> > - Output of the following command *after* requesting a resize:
> >
> > $ virsh domblkinfo $instance_uuid $target_dev
> >
> > - Output of the following commands once confirmed the resize didn't
> >    happen within the domain:
> >
> > $ virsh blockresize $instance_uuid $rbd_path $new_size
> > $ virsh domblkinfo $instance_uuid $target_dev
> >
> >  From what you've said above this smells like a libvirt/QEMU bug but I
> > don't have a rbd env to hand to confirm things at the moment.
> >
> > Cheers,
> >
>
> I have just been trying to reproduce the issue, but in all my new
> attempts it just worked as expected:
>
> > [162262.926512] sd 0:0:0:1: Capacity data has changed
> > [162262.932868] sd 0:0:0:1: [sdb] 6291456 512-byte logical blocks:
> > (3.22 GB/3.00 GiB)
> > [162262.933061] sdb: detected capacity change from 2147483648 to
> > 3221225472
>
>
> Sorry about the noise then.
>
> The only "bugs" to report are the usability issues of Horizon not
> offering "in-use" extension of volume as far as I can see and the
> pending support in the openstack cli
> (https://bugs.launchpad.net/cinder/+bug/1871759).

i have done a live extend using cinder client before.

sean at p50:~$ cinder --help extend
usage: cinder extend <volume> <new_size>

Attempts to extend size of an existing volume.

Positional Arguments:
  <volume>    Name or ID of volume to extend.
  <new_size>  New size of volume, in GiBs.


so it does work provided you have not used the nova workaround config options for host mounting
the rbd volumens.
https://docs.openstack.org/nova/latest/configuration/config.html#workarounds.rbd_volume_local_attach
that will go away shortly proably in the xena release but if you enable that you can resize volumnes that
are in use.

so ya i think the only bugs are really not bugs but RFEs
openstack client does not have parity with cinder client and nor does horizon.
a lack of feature in the latter too is not really a bug just no one has implmented it yet so there is a gap.

from the api side and a nova persoection i think it should work you just need to use a clint that supprot it.

>
>
>
> Thanks again,
> Regards
>
>
> Christian
>
>
>
>
>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210217/02336ccf/attachment-0001.html>


More information about the openstack-discuss mailing list