Bug 2028628 - cephadm-clients playbook keyring isn't copied with the same name as specified by the keyring parameter
Summary: cephadm-clients playbook keyring isn't copied with the same name as specified...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 5.2
Assignee: Guillaume Abrioux
QA Contact: Ameena Suhani S H
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks: 2024344 2102272
TreeView+ depends on / blocked
 
Reported: 2021-12-02 20:10 UTC by Mary Frances Hull
Modified: 2022-08-09 17:37 UTC (History)
14 users (show)

Fixed In Version: cephadm-ansible-1.1.0-1.el8cp
Doc Type: Bug Fix
Doc Text:
.`cephadm` supports copying client keyrings with different names Previously, `cephadm` would enforce a file name at the destination, when copying the client keyring: ceph.keyring. With the current fix, `cephadm` supports copying the client keyring with a different name, eliminating the issue of automatic renaming when copied.
Clone Of: 2024344
Environment:
Last Closed: 2022-08-09 17:36:46 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph cephadm-ansible pull 60 0 None Merged cephadm-clients: add new parameter 'keyring_dest' 2022-07-07 05:30:22 UTC
Red Hat Issue Tracker RHCEPH-2487 0 None None None 2021-12-02 20:14:11 UTC
Red Hat Product Errata RHSA-2022:5997 0 None None None 2022-08-09 17:37:10 UTC

Comment 15 errata-xmlrpc 2022-08-09 17:36:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5997


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