Bug 1523703 - The cephfs user guide should explain how to obtain a secretfile
Summary: The cephfs user guide should explain how to obtain a secretfile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 3.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: z1
: 3.2
Assignee: John Brier
QA Contact: Vasishta
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1668330
TreeView+ depends on / blocked
 
Reported: 2017-12-08 16:10 UTC by Daniel Messer
Modified: 2019-03-28 14:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-28 14:17:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Messer 2017-12-08 16:10:50 UTC
Description of problem:

Right now, when setting up a client for use with CephFS the docs talk about creating a user with cephx. It then asks the reader to mount the CephFS with a username and secretfile. However nowhere it's explained how to actually get / create this secret file. One has to google/go to docs.ceph.com for this to learn that it's actually just the keyring in cleartext.

Version-Release number of selected component (if applicable):

RHCS 3.0

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/ceph_file_system_guide/deploying-ceph-file-systems#manually-mounting-the-ceph-file-system-as-a-kernel-client

Comment 5 John Brier 2018-11-08 00:42:41 UTC
I ran into this too. I tried passing in the keyring file:

[root@jb-rhel-client ceph]$ mount -t ceph 192.168.122.213:/ /mnt/cephfs/ -o name=1,secretfile=/etc/ceph/ceph.client.1.keyring
secret is not valid base64: Invalid argument.
adding ceph secret key to kernel failed: Invalid argument.
failed to parse ceph_options


Googled 'secret is not valid base64: Invalid argument.' and found the answer here:

http://lists.ceph.com/pipermail/ceph-users-ceph.com/2017-July/019385.html

It worked right away.


Note You need to log in before you can comment on or make changes to this bug.