That key should have been created when the cluster was. The orchestration
software (ceph-deploy, ceph-ansible, or whatever you're using) is
responsible for putting it in place on the local machine if needed, but in
your case you should just need to fetch it. ("get-or-create" rather than
"new", maybe? Not certain of the syntax but you want to fetch what exists
rather than forcing a new creation that doesn't match the existing one.)
-Greg

On Thu, May 31, 2018 at 10:41 AM Marc Roos <[email protected]> wrote:

>
> I don’t have the /var/lib/ceph/bootstrap-osd/ceph.keyring, how should I
> create this file?
>
>
> [@ ~]# ceph-disk prepare --bluestore --zap-disk --dmcrypt /dev/sdg
> Creating new GPT entries.
> The operation has completed successfully.
> mke2fs 1.42.9 (28-Dec-2013)
> Filesystem label=
> OS type: Linux
> Block size=1024 (log=0)
> Fragment size=1024 (log=0)
> Stride=4 blocks, Stripe width=4 blocks
> 2560 inodes, 10240 blocks
> 512 blocks (5.00%) reserved for the super user
> First data block=1
> Maximum filesystem blocks=10485760
> 2 block groups
> 8192 blocks per group, 8192 fragments per group
> 1280 inodes per group
> Superblock backups stored on blocks:
>      8193
>
> Allocating group tables: done
> Writing inode tables: done
> Creating journal (1024 blocks): done
> Writing superblocks and filesystem accounting information: done
>
> command_with_stdin: 2018-05-31 19:14:01.018049 7f60281cc700 -1 auth:
> unable to find a keyring on /var/lib/ceph/bootstrap-osd/ceph.keyring: (2
> ) No such file or directory
> 2018-05-31 19:14:01.018401 7f60281cc700 -1 monclient: ERROR: missing
> keyring, cannot use cephx for authentication
> 2018-05-31 19:14:01.018404 7f60281cc700  0 librados:
> client.bootstrap-osd initialization error (2) No such file or directory
> [errno 2] error connecting to the cluster
>
> '['ceph', '--cluster', 'ceph', '--name', 'client.bootstrap-osd',
> '--keyring', '/var/lib/ceph/bootstrap-osd/ceph.keyring', '-i', '-',
> 'osd', 'new', 'e590f7e2-9892-4c2f-bf5b-6ce7d1b3d488']' failed with
> status code 1
> _______________________________________________
> ceph-users mailing list
> [email protected]
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to