Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1679009

Summary: No ceph.client.1.keyring file
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jos Collin <jcollin>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2CC: agunn, asriram, hyelloji, kdreyer
Target Milestone: rcKeywords: NoDocsQEReview
Target Release: 4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 00:18:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jos Collin 2019-02-20 05:38:17 UTC 
Description of problem:

[1] says:

"scp root@<monitor>:/etc/ceph/ceph.client.1.keyring /etc/ceph/ceph.client.1.keyring"
and
"[root@client ~]# scp root.0.1:/ceph.client.1.keyring /etc/ceph/ceph.client.1.keyring"

But there is no such file called ceph.client.1.keyring created anywhere in the monitor node. However, the keys are getting created and the user has to copy it and create a file called ceph.client.1.keyring in the client node manually.

[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/ceph_file_system_guide/#creating-ceph-file-system-client-users

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

How reproducible:
Always

Steps to Reproduce:
Mentioned in the Description

Actual results:
'ceph auth get-or-create' command specified in [1] doesn't create a file named ceph.client.1.keyring on the monitor node.

Expected results:


Additional info:
Comment 1 Giridhar Ramaraju 2019-08-05 13:11:00 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 2 Giridhar Ramaraju 2019-08-05 13:12:02 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 3 Giridhar Ramaraju 2019-08-20 06:57:56 UTC 
Level setting the severity of this defect to "High" with a bulk update. Pls refine it to a more closure value, as defined by the severity definition in https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity