Just for the records:
After recreating the config from scratch (after the upgrade to
ceph-iscsi-3.0) the problem went away. I can use the gateway without
client.admin access now.
thanks
matthias
Am 01.04.19 um 17:05 schrieb Jason Dillaman:
What happens when you run "rados -p rbd lock list ga
running "rados -p rbd lock list gateway.conf" gives:
{"objname":"gateway.conf","locks":[{"name":"lock"}]}
To be sure I stopped all related services (tcmu-runner, rbd-target-gw,
rbd-target-api) on both gateways and ran "rados -p rbd lock list
gateway.conf" again, result was the same as above. Ho
What happens when you run "rados -p rbd lock list gateway.conf"?
On Fri, Mar 29, 2019 at 12:19 PM Matthias Leopold
wrote:
>
> Hi,
>
> I upgraded my test Ceph iSCSI gateways to
> ceph-iscsi-3.0-6.g433bbaa.el7.noarch.
> I'm trying to use the new parameter "cluster_client_name", which - to me
> - so
Hi,
I upgraded my test Ceph iSCSI gateways to
ceph-iscsi-3.0-6.g433bbaa.el7.noarch.
I'm trying to use the new parameter "cluster_client_name", which - to me
- sounds like I don't have to access the ceph cluster as "client.admin"
anymore. I created a "client.iscsi" user and watched what happene
