Problem with volume resize after upgrade from 4.22.0 to 4.22.1

[sbrueseke]

Hello, we found a strange situation yesterday and hope somebody can try to recreate it.
We are using KVM hypervisor with linstor storage. We needed to resize a volume of an instance, which we successfully did in the past on a running vm. This time it did not work as expected. From ACS and linstor everything looks good, but inside the instance the volume still did had the same size. After stopping the vm and starting it again, the new size was shown and could be used. We see this behavior only on instances which were not stopped and started since our upgrade to 4.22.1. New instances are working as expected.

virsh domblkinfo i-29-423-VM vda
Capacity: 53688164352
Allocation: 53688139776
Physical: 107376365568

It looks like the new Capacity is not shown in virsh domblkinfo and we see some changes in virsh dumpxml regarding source dev.

Is anybody able to recreate this behavior? You need to run on 4.22.1 and you need access to instances which are not being stopped since the upgrade.