I wanted to see the fail of the initial drive_add and I was able to create: virsh qemu-monitor-command --hmp instance-0000001a 'drive_add 1 file=rbd:cinder-ceph/volume-8ab7473e-c34c-421a-b6d9-b18a9fa8788a:id=nova-compute:auth_supported=cephx\;none:mon_host=10.5.26.60\:6789\;10.5.26.61\:6789\;10.5.26.62\:6789,password-secret=virtio-disk0-secret1,format=raw,if=none,id=drive-virtio-disk1,serial=8ab7473e-c34c-421a-b6d9-b18a9fa8788a,cache=none'
That is even closer to the root cause and shows: Block format 'raw' does not support the option 'password-secret' >From there I found that this is an issue with old/new syntax and it needs an >attribute prefix on the old syntax used. Fix: password-secret -> file.password-secret Then it will complain about lacking the secret, but that is ok I haven't added one in my manual flow. After that was known I was also able to find: - https://www.redhat.com/archives/libvir-list/2016-August/msg00783.html - https://libvirt.org/git/?p=libvirt.git;a=commit;h=d53d465083edeb64cc7b78249c030734c0d91c6b Fix is in >=2.2 change that started to fail in 1.3.5. Given that we have: - xenial 1.3.1-1ubuntu10.8 - yakkety 2.1.0-1ubuntu9 - zesty 2.5.0-3ubuntu3 We only need an SRU for Yakkety. ** Summary changed: - libvirtError: internal error: unable to execute QEMU command 'device_add': Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk1' + libvirt uses password-secret on old style drive_add syntax ** Also affects: qemu (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672367 Title: libvirt uses password-secret on old style drive_add syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1672367/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
