rbd driver fails to create a new volume

[Tomas Hlavacek]

When I try to create a new volume in Ceph RBD pool using virt-manager over eoan server with libvirt I get the following error:

Error creating vol: Couldn't create storage volume 'vol': 'unsupported configuration: only RAW volumes are supported by this storage pool'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtinst/storage.py", line 682, in install
    vol = self.pool.createXML(xml, createflags)
  File "/usr/lib/python3/dist-packages/libvirt.py", line 3220, in createXML
    if ret is None:raise libvirtError('virStorageVolCreateXML() failed', pool=self)
libvirt.libvirtError: unsupported configuration: only RAW volumes are supported by this storage pool

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createvol.py", line 339, in _async_vol_create
    vol.install(meter=meter)
  File "/usr/share/virt-manager/virtinst/storage.py", line 692, in install
    "'%s': '%s'" % (self.name, str(e)))
RuntimeError: Couldn't create storage volume 'vol': 'unsupported configuration: only RAW volumes are supported by this storage pool'

It is likely known bug that is already fixed in upstream: https://bugzilla.redhat.com/show_bug.cgi?id=1724065

[Christian Ehrhardt  (paelzer)]

Thank you for your report Tomas!

Broken since v5.2.0 (offending commit 035db373)
Fixed since v5.6.0 (fix in commit 5d746193)

Therefore affected are Focal and Eoan.

I'll take care of this for Focal as part of a merge of a new libvirt anyway.
From there we can consider an SRU for Eoan afterwards.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libvirt - 6.0.0-0ubuntu1

---------------
libvirt (6.0.0-0ubuntu1) focal; urgency=medium

  * Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
    Among many other new features and fixes this includes fixes for:
    - LP: #1859253 - rbd driver fails to create a new volume
    - LP: #1858341 - rbd driver does not list all volumes in pool
    - LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
    - LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
    - LP: #1848229 - enable ppc64el to use ccf-assist feature
    - LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
    - LP: #1853317 - CCW IPL support to boot from ECKD DASDs
    - LP: #1859506 - security: AppArmor profile fixes for swtpm
    Remaining changes:
    - Disable libssh2 support (universe dependency)
    - Disable firewalld support (universe dependency)
    - Set qemu-group to kvm (for compat with older ubuntu)
    - Additional apport package-hook
    - Autostart default bridged network (As upstream does, but not Debian).
      In addition to just enabling it our solution provides:
      + do not autostart if subnet is already taken (e.g. in guests).
      + iterate some alternative subnets before giving up
    - d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
      the group based access to libvirt functions as it was used in Ubuntu
      for quite long.
      + d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
        due to the group access change.
      + d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
        group.
    - ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
    - Update Vcs-Git and Vcs-Browser fields to point to launchpad
    - Update README.Debian with Ubuntu changes
    - Enable some additional features on ppc64el and s390x (for arch parity)
      + systemtap, zfs, numa and numad on s390x.
      + systemtap on ppc64el.
    - d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
    - Further upstreamed apparmor Delta, especially any new one
      Our former delta is split into logical pieces and is either Ubuntu only
      or is part of a continuous upstreaming effort.
      Listing related remaining changes in debian/patches/ubuntu-aa/:
    - fix autopkgtests
      + d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
        vmlinuz available and accessible (Debian bug 848314)
      + d/t/control: fix smoke-qemu-session by ensuring the service will run
        installing libvirt-daemon-system
      + d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
        long as the following undefine succeeds
      + d/t/smoke-lxc: use systemd instead of sysV to restart the service
    - dnsmasq related enhancements
      + run dnsmasq as libvirt-dnsmasq (LP: 1743718)
      + d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
      + d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
        on purge
      + d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
        libvirt-dnsmasq and adapt t...

[Christian Ehrhardt  (paelzer)]

FYI: Focal is done, checking if this would be a good SRU follows after som e more urgent tasks

In the meantime you could help the SRU processing [1] by providing step-by-step commands/configs to reproduce the reported issue.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates

[Christian Ehrhardt  (paelzer)]

Lacking steps to reproduce I'm not going to SRU this.
Upgrading to Focal (also being an LTS) is in many cases the better option anyway.

Marking the Eoan as Won't Fix unless someone speaks up (since the report there was no further activity or people affected so far) for this to be more important and adding clear steps to recreate this on the SRU [1].

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template