[ceph-users] Re: Ceph client failed to mount RBD device after reboot

2019-09-06 Thread JC Lopez
Hi ceph auth caps client.n01 mon ‘profile rbd’ osd ‘profile rbd’ should do the trick. JC > On Sep 6, 2019, at 05:23, Vang Le-Quy wrote: > > Hi Jason > My client key content looks like the following: > > #[ > [client.n01] > key = AQA301KcfFVtKxAAyJxY9uTvNh3gn7eH3iHhKw==

[ceph-users] Re: using non client.admin user for ceph-iscsi gateways

2019-09-06 Thread Wesley Dillingham
Thanks for the info: https://docs.ceph.com/docs/master/rbd/iscsi-target-cli/ Presented as a comment in the sample config file: # Place a copy of the ceph cluster's admin keyring in the gateway's /etc/ceph # drectory and reference the filename here gateway_keyring = ceph.client.admin.keyring

[ceph-users] Re: using non client.admin user for ceph-iscsi gateways

2019-09-06 Thread Jason Dillaman
On Fri, Sep 6, 2019 at 12:00 PM Wesley Dillingham wrote: > > the iscsi-gateway.cfg seemingly allows for an alternative cephx user other > than client.admin to be used, however the comments in the documentations says > specifically to use client.admin. Hmm, can you point out where this is in

[ceph-users] using non client.admin user for ceph-iscsi gateways

2019-09-06 Thread Wesley Dillingham
the iscsi-gateway.cfg seemingly allows for an alternative cephx user other than client.admin to be used, however the comments in the documentations says specifically to use client.admin. Other than having the cfg file point to the appropriate key/user with "gateway_keyring" and giving that

[ceph-users] Re: Ceph client failed to mount RBD device after reboot

2019-09-06 Thread Vang Le-Quy
Hi Jason My client key content looks like the following: #[ [client.n01] key = AQA301KcfFVtKxAAyJxY9uTvNh3gn7eH3iHhKw== # So Paul and you may be right, the key lacks suitable caps. Can I just manually add caps to the key file or it has to be regenerated from the CEPH

[ceph-users] Re: Followup: weird behaviour with ceph osd pool create and the "crush-rule" parameter (suddenly changes behaviour)

2019-09-06 Thread aoanla
Nice thought but no: in the case in the original post "ec4pool" had not been used as the name for a pool, or a profile, before. (and trying out combinations of deleting old profiles did not change the behavior). ___ ceph-users mailing list --

[ceph-users] Re: Ceph client failed to mount RBD device after reboot

2019-09-06 Thread Jason Dillaman
On Fri, Sep 6, 2019 at 7:33 AM Vang Le-Quy wrote: > Hi Paul > > Thank you for suggestion. > > Firstly, a correction “I am suspecting that there is a bug in > 12.2.8-0ubuntu0.18.04.1” > is incorrect. I meant that version 12.2.8-0ubuntu0.18.04.1 on node N01 > works, . 12.2.12-0ubuntu0.18.04.2 is

[ceph-users] Re: Ceph client failed to mount RBD device after reboot

2019-09-06 Thread Vang Le-Quy
Hi Paul Thank you for suggestion. Firstly, a correction “I am suspecting that there is a bug in 12.2.8-0ubuntu0.18.04.1” is incorrect. I meant that version 12.2.8-0ubuntu0.18.04.1 on node N01 works, . 12.2.12-0ubuntu0.18.04.2 is having problem. After upgrading to version

[ceph-users] Re: Ceph client failed to mount RBD device after reboot

2019-09-06 Thread Paul Emmerich
failure to break locks is usually due to incorrect permissions on the key, check if the client key has "profile rbd" mon permissions -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49 89

[ceph-users] Re: RGW bucket check --check-objects -fix failed

2019-09-06 Thread EDH - Manuel Rios Fernandez
Checking the shards, bucket got 64. But shard 48efb8c3-693c-4fe0-bbe4-fdc16f590a82.16313306.1.1 seems missing. Radosgw-admin fix wont recreate again, any recommendation? Maybe change shard numbers to lower? Regards Manuel De: EDH - Manuel Rios Fernandez Enviado el: jueves, 5