On 03/05/2015 03:40 AM, Josh Durgin wrote:
It looks like your libvirt rados user doesn't have access to whatever
pool the parent image is in:
librbd::AioRequest: write 0x7f1ec6ad6960
rbd_data.24413d1b58ba.0000000000000186 1523712~4096 should_complete: r
= -1
-1 is EPERM, for operation not permitted.
Check the libvirt user capabilites shown in ceph auth list - it should
have at least r and class-read access to the pool storing the parent
image. You can update it via the 'ceph auth caps' command.
Josh,
All images, parent, snapshot and clone reside on the same pool
(libvirt-pool *) and the user (libvirt) seems to have the proper
capabilities. See:
client.libvirt
key: xxxx
caps: [mon] allow r
caps: [osd] allow class-read object_prefix rbd_children, allow rw
class-read pool=rbd
This same pool contains other (flat) images used to back my production
VMs. They are all accessed with this same user and there have been no
problems so far. I just can't seem able to use cloned images.
-K.
* In my original email describing the problem I used 'rbd' instead of
'libvirt-pool' for the pool name for simplicity. As more and more
configuration items are requested, it makes more sense to use the real
pool name to avoid causing any misconceptions.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
