Back to bug 2028628
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2021-12-02 20:14:11 UTC | Link ID | Red Hat Issue Tracker RHCEPH-2487 | |
| Mary Frances Hull | 2021-12-02 20:19:24 UTC | Blocks | 2024344 | |
| Depends On | 2024344 | |||
| Adam King | 2022-03-08 14:50:07 UTC | CC | adking | |
| Status | NEW | ASSIGNED | ||
| Guillaume Abrioux | 2022-04-26 09:01:37 UTC | Link ID | Github ceph/cephadm-ansible/pull/60 | |
| Guillaume Abrioux | 2022-05-13 15:26:20 UTC | CC | tsaito | |
| Status | ASSIGNED | POST | ||
| Guillaume Abrioux | 2022-05-13 15:26:50 UTC | Component | Ceph-Ansible | Cephadm |
| Docs Contact | asriram | |||
| QA Contact | amsyedha | sunnagar | ||
| CC | ceph-qe-bugs | |||
| Red Hat Bugzilla | 2022-05-18 11:11:33 UTC | CC | gsitlani | |
| Ken Dreyer (Red Hat) | 2022-05-24 20:11:19 UTC | Fixed In Version | cephadm-ansible-1.1.0-1.el8cp | |
| Status | POST | MODIFIED | ||
| Keywords | Rebase | |||
| errata-xmlrpc | 2022-05-24 23:38:23 UTC | Status | MODIFIED | ON_QA |
| Red Hat Bugzilla | 2022-05-26 08:30:25 UTC | CC | ceph-qe-bugs | |
| Manasa | 2022-05-27 06:49:27 UTC | QA Contact | sunnagar | amsyedha |
| CC | mgowri | |||
| Ameena Suhani S H | 2022-06-02 21:12:02 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2022-07-06 07:20:18 UTC | CC | akraj | |
| Blocks | 2102272 | |||
| Docs Contact | asriram | akraj | ||
| Flags | needinfo?(gabrioux) | |||
| Guillaume Abrioux | 2022-07-07 05:33:09 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Flags | needinfo?(gabrioux) | |||
| Doc Text | Cause: cephadm enforces the file name at the destination when copying the client keyring (ceph.keyring) Consequence: when copying a keyring with a different name, it gets renamed. Fix: make cephadm support copying with a different keyring name. Result: the keyring doesn't get renamed once it's copied. |
|||
| Akash Raj | 2022-07-13 06:20:03 UTC | Doc Text | Cause: cephadm enforces the file name at the destination when copying the client keyring (ceph.keyring) Consequence: when copying a keyring with a different name, it gets renamed. Fix: make cephadm support copying with a different keyring name. Result: the keyring doesn't get renamed once it's copied. | .`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. |
| Flags | needinfo?(gabrioux) | |||
| Guillaume Abrioux | 2022-07-18 07:48:00 UTC | 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. | .`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. |
| Guillaume Abrioux | 2022-07-18 07:48:16 UTC | Flags | needinfo?(akraj) | |
| Guillaume Abrioux | 2022-07-18 08:05:56 UTC | Flags | needinfo?(gabrioux) | |
| Akash Raj | 2022-07-20 04:33:49 UTC | Flags | needinfo?(akraj) | |
| errata-xmlrpc | 2022-08-09 09:55:11 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:36:46 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-08-09 17:36:46 UTC | |||
| errata-xmlrpc | 2022-08-09 17:37:11 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2028628