Interesting that you have no cinder-ceph volume at all from libvirt's
POV.
We no more have to look at/inside the guest (e.g. lsblk).
The breaking point seems to be between openstack and libvirt.
Openstack thinks it has told libvirt to attach the volume
| volumes_attached | id='541bf46c-8ccf-4158-8565-6204a1d8350f' |
But libvirt does not know about it as your `virsh domblklist` is empty.
@James/Corey - I'd like to reiterate my question of comment #2 if you
have seen such a thing?
Furthermore is there a place in Openstack that would allow us to trace
what openstack has told libvirt to do to atatch the device (and what the
answer was)?
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825356
Title:
libvirt silently fails to attach a cinder ceph volume
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1825356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
