Bug 1956956

Summary: Command to generate crash key fails after upgrade to 5.0
Product: Red Hat Ceph Storage Reporter: Pawan <pdhiran>
Component: RADOSAssignee: Neha Ojha <nojha>
Status: NEW --- QA Contact: Pawan <pdhiran>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.0CC: akupczyk, bhubbard, ceph-eng-bugs, dzafman, kchai, nojha, rzarzyns, sseshasa, vumrao
Target Milestone: ---Flags: pdhiran: needinfo? (nojha)
Target Release: 5.1   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Comment 6 Pawan 2021-06-10 12:31:27 UTC
Yeah neha, the crash module is working as expected after upgrade.

Can you help clarify this?
1. Is the Crash keyring along with the authorizations are not created in /etc/ceph folder in 5.0?
2. Is the assumption correct? that the keys in upgraded cluster failed to create since authorizations related to CRASH were already present?
3. Is this a expected change in 5.0? Do we need to perform additional tests in this area if it has been modified in 5.0?
4. Since no keyring files are generated in 5.0, does doc need to be updated for [1]?
[1]. https://docs.ceph.com/en/latest/man/8/ceph-create-keys/
5. Should the documentation for CRASH module be updated [3] for 5.0?( parts relating to enabling and keys generation )
[3]. https://docs.ceph.com/en/latest/mgr/crash/#enabling