Hi, I was playing with oVirt/Cinder integration and faced the issue. At the same time virsh on CentOS 7.3 was working fine with RBD images. So, as a workaround following procedure can be used to permanently set the secret on libvirt host:
# vi /tmp/secret.xml <secret ephemeral='no' private='no'> <uuid>db11828c-f9e8-48cb-81dd-29fc00ec1c14</uuid> <usage type='ceph'> <name>admin</name> </usage> </secret> # virsh secret-define /tmp/secret.xml # virsh secret-set-value db11828c-f9e8-48cb-81dd-29fc00ec1c14 <base64-password> Googleme: the VDSM error was: Thread-289::ERROR::2016-12-20 12:44:39,306::vm::765::virt.vm::(_startUnderlyingVm) vmId=`16889d09-14b1-455b-ab2c-fcbd697b8f59`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 706, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 1996, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 917, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: Secret not found: no secret with matching uuid 'db11828c-f9e8-48cb-81dd-29fc00ec1c14' Thread-289::INFO::2016-12-20 12:44:39,309::vm::1308::virt.vm::(setDownStatus) vmId=`16889d09-14b1-455b-ab2c-fcbd697b8f59`::Changed state to Down: Secret not found: no secret with matching uuid 'db11828c-f9e8-48cb-81dd-29fc00ec1c14' (code=1) > 20 дек. 2016 г., в 3:06, Mike Lowe <j.michael.l...@gmail.com> написал(а): > > Not that I’ve found, it’s a little hard to search for. I believe it’s > related to this libvirt mailing list thread > https://www.redhat.com/archives/libvir-list/2016-October/msg00396.html > <https://www.redhat.com/archives/libvir-list/2016-October/msg00396.html> > You’ll find this in the libvirt qemu log for the instance 'No secret with id > 'scsi0-0-0-1-secret0’’ and this in the nova-compute log 'libvirtError: > internal error: unable to execute QEMU command '__com.redhat_drive_add': > Device 'drive-scsi0-0-0-1' could not be initialized’. I was able to yum > downgrade twice to get to something from the 1.2 series. > > >> On Dec 19, 2016, at 6:40 PM, Jason Dillaman <jdill...@redhat.com >> <mailto:jdill...@redhat.com>> wrote: >> >> Do you happen to know if there is an existing bugzilla ticket against >> this issue? >> >> On Mon, Dec 19, 2016 at 3:46 PM, Mike Lowe <j.michael.l...@gmail.com >> <mailto:j.michael.l...@gmail.com>> wrote: >>> It looks like the libvirt (2.0.0-10.el7_3.2) that ships with centos 7.3 is >>> broken out of the box when it comes to hot plugging new virtio-scsi devices >>> backed by rbd and cephx auth. If you use openstack, cephx auth, and >>> centos, I’d caution against the upgrade to centos 7.3 right now. >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@lists.ceph.com <mailto:ceph-users@lists.ceph.com> >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> >> >> >> -- >> Jason > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Dmitry Glushenok Jet Infosystems
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com