Github user mlsorensen commented on the pull request:
https://github.com/apache/cloudstack/pull/281#issuecomment-104692430
It was fixed for QCOW2 and LVM, back in January or February (unless
something has changed since then). It may be fine for RBD, I just wanted to
bring it up as a caution. My impression was that there might be an issue with
the java bindings, either a bug or a missing call. If I remember correctly,
there are two things, there's libvirt managing volumes, and libvirt managing
block devices attached to VMs, and they are not the same thing. Resizing a
libvirt volume didn't necessarily notify any VM process using that volume of
the change, nor resize the block device attached to the live VM. 'virsh
blockresize' does this correctly at both the libvirt volume and VM block,
though, so we just went back to the script rather than trying to figure out how
to patch the java libvirt bindings.
Just make sure the existing behavior is not changed and test that you can
stop/start and read/write the root disk fine post a resize.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
