Comment 4 for bug 1735931

Liam,
I should have said pool, not volume, it is a pool for thin provisioning,
you can see it in my original output. As you can see cinder-volume-pool
is 9.5GB while it should be twice that size. It has 2x size when I put
both block devices to charm from start.

What you showed in you other post, yes, that is also what I see, VG is
extended, that works. But the pool which is then available for thin
volume allocation is not extended.

I looked at charm code, and if I am reading it right, it only
allocates/extends VG, rest is probably executed in Cinder itself later -
that I am just guessing, because I did not find any LV or LV-pool
related code in hooks.
In that case it is not bug in code but maybe missing functionality? I
think common expectation is when you add block device to charm, it
should be reflected in cinder then.

I am 95% sure I used cs:cinder-264, I am on 17.10, juju is 2.3-beta1.
But if what I wrote above is correct, it does not matter, LV/LVpool
extend code is not in cinder charm.

On 05.12.2017 14:57, Liam Young wrote:
> Actually we may be on cross purposes here. I would not expect the
> logical volumes to be extended as they relate to a specific cinder
> volume and I see in your paste that you have 2 physical volumes listed
> in the output from vgs which looks correct.
>
> ** Changed in: charm-cinder
> Status: New => Incomplete
>