On Wed, Nov 14, 2012 at 4:20 AM, Andrey Korolyov <andrey@xxxxxxx> wrote: > Hi, > In the 0.54 cephx is probably broken somehow: > > $ ceph auth add client.qemukvm osd 'allow *' mon 'allow *' mds 'allow > *' -i qemukvm.key > 2012-11-14 15:51:23.153910 7ff06441f780 -1 read 65 bytes from qemukvm.key > added key for client.qemukvm > > $ ceph auth list > ... > client.admin > key: [xxxxxx] > caps: [mds] allow * Note that for mds you just specify 'allow' and not 'allow *'. It shouldn't affect the stuff that you're testing though. > caps: [mon] allow * > caps: [osd] allow * > client.qemukvm > key: [yyyyyy] > caps: [mds] allow * > caps: [mon] allow * > caps: [osd] allow * > ... > $ virsh secret-set-value --secret uuid --base64 yyyyyy > set username in the VM` xml... > $ virsh start testvm > kvm: -drive file=rbd:rbd/vm0:id=qemukvm:key=yyyyyy:auth_supported=cephx\;none:mon_host=192.168.10.125\:6789\;192.168.10.127\:6789\;192.168.10.129\:6789,if=none,id=drive-virtio-disk0,format=raw: > could not open disk image > rbd:rbd/vm0:id=qemukvm:key=yyyyyy:auth_supported=cephx\;none:mon_host=192.168.10.125\:6789\;192.168.10.127\:6789\;192.168.10.129\:6789: > Operation not permitted > $ virsh secret-set-value --secret uuid --base64 xxxxxx > set username again to admin for the VM` disk > $ virsh start testvm > Finally, vm started successfully. > > All rbd commands issued from cli works okay with the appropriate > credentials, qemu binary was linked with same librbd as running one. > Does anyone have a suggestion? There wasn't any change that I'm aware of that should make that happening. Can you reproduce it with 'debug ms = 1' and 'debug auth = 20'? Thanks, Yehuda -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
