Bug 2161545
| Summary: | [cee/sd][cephadm] cephadm removes ceph.conf and admin keyring files post node reboot | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Lijo Stephen Thomas <lithomas> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Mohit Bisht <mobisht> |
| Severity: | medium | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | adking, akraj, cephqe-warriors, gjose, mobisht, saraut, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 6.1z1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-17.2.6-84.el9cp | Doc Type: | Bug Fix |
| Doc Text: |
.The config or keyring files are no longer temporarily removed from the nodes
Previously, in `cephadm`, the calculation of where client config/keyrings files should be written would occasionally end up empty. Due to this, config/keyring files are temporarily removed from the nodes where they should be left alone until the next checks and the correct calculation.
With this fix, the timing of the calculation is altered and the keyring/conf files are no longer randomly removed from the nodes temporarily.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-03 16:45:09 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2221020 | ||
|
Description
Lijo Stephen Thomas
2023-01-17 08:42:21 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 (Red Hat Ceph Storage 6.1 Bug Fix 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/RHBA-2023:4473 |