FYI - The referenced comment is the Tempest test that James uses and it
contains a ceph block attach which would trigger the bug. Executing it
against the proposed version is "verification-done" for it although it
was forgotten to link this bug due to our merge of this and the next SRU
upload.

** Description changed:

  [Impact]
  
-  * Using ceph (rbd) devices fail to be attached to a guest
+  * Using ceph (rbd) devices fail to be attached to a guest
  
-  * Regression when updating from Xenial to Yakkety (or matching cloud
+  * Regression when updating from Xenial to Yakkety (or matching cloud
  archives)
  
-  * backport of upstream fixes the command string passed to qemu
+  * backport of upstream fixes the command string passed to qemu
  
  [Test Case]
  
-  * Attach a rbd device to a guest via libvirt.
-    * The openstack Team does so from Openstack
-    * To do so manually (hard) you could hot-add an xml snipped like the one 
in comment #2 (but thta still needs a ceph with matching config up)
-    * since this is complex please see below for all the tests already 
performed
+  * Attach a rbd device to a guest via libvirt.
+    * The openstack Team does so from Openstack
+    * To do so manually (hard) you could hot-add an xml snipped like the one 
in comment #2 (but thta still needs a ceph with matching config up)
+    * since this is complex please see below for all the tests already 
performed
+ 
+  * An "easier" testcase is to run the Tempest suite which contains a 
+    testcase triggering the bug according to James Page
  
  [Regression Potential]
  
-  * It changes the device string creation, so it in theory break other device 
attaching actions (if any). Yet the chances for a regression should be low 
because:
-    1. the fix is upstream a while now (and needed no follow up)
-    2. current main user of that password feature is broken without (ceph/rbd)
-    3. no effect on other disk attachments (others are not using password)
+  * It changes the device string creation, so it in theory break other device 
attaching actions (if any). Yet the chances for a regression should be low 
because:
+    1. the fix is upstream a while now (and needed no follow up)
+    2. current main user of that password feature is broken without (ceph/rbd)
+    3. no effect on other disk attachments (others are not using password)
  
  [Other Info]
-  
-  * n/a
  
+  * n/a
  
  I'm unable to attach ceph rbd devices to qemu instances (via OpenStack -
  but I don't think the issue is in OpenStack per-say because the same
  codebase against the Xenial libvirt/qemu stack is OK).
  
  libvirtError: internal error: unable to execute QEMU command
  'device_add': Property 'virtio-blk-device.drive' can't find value
  'drive-virtio-disk1'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: qemu-system-x86 1:2.6.1+dfsg-0ubuntu5.3
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Mar 13 12:37:22 2017
  Ec2AMI: ami-0000058e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr13.1.2:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 13.1.2
  dmi.sys.vendor: OpenStack Foundation

-- 
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

Reply via email to