Dmitrii Shcherbakov (dmitriis) wrote on 2017-02-02: @beisner
Had issues with deployment - for some reason a couple of undercloud VMs got stuck (juju was waiting for a machine allocation while it already booted) after running juju-deployer. Had to manually remove affected units and 'juju add-unit' them to get it working. Nevertheless, here's the result with a fully-deployed xenial-mitaka next.yaml bundle from the o-c-t (amd64, serverstack, some package versions included in the paste): https://pastebin.canonical.com/178064/ I checked it from the nova, libvirt, qemu and guest POV - it looks good I wasn't able to reproduce the original issue. virtio-blk devices are used by default so PCI-hotplug (http://wiki.qemu.org/Features/PCIBridgeHotplug) was triggered inside the guest kernel. I verified that libvirt has set up an RBD for the added virtio-blk device and that it was visible by qemu (checked via QMP) and the guest (dmesg + lsblk). Removal worked just fine as well. Double addition of the same volume to the same VM without reboot worked fine too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
