Bug 2024720
| Summary: | [Workload-DFG] ceph failed to probe daemons or devices | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tim Wilkinson <twilkins> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Manasa <mgowri> |
| Severity: | high | Docs Contact: | Karen Norteman <knortema> |
| Priority: | high | ||
| Version: | 5.1 | CC: | adking, akraj, kdreyer, mgowri, racpatel, tserlin, vereddy, vumrao |
| Target Milestone: | --- | Keywords: | Rebase |
| Target Release: | 5.2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.8-2.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.`cephadm` verifies if the `fsid` of the daemon it was inferring a config from matches the expected `fsid`
Previously, in `cephadm`, there was no check to verify if the `fsid` of the daemon it was inferring a configuration from matched the expected `fsid`. Due to this, if users had a `/var/lib/ceph/_FSID_/_DAEMON_NAME_` directory with an `fsid` other than the expected one, the configuration from that daemon directory would still be inferred.
With this fix, checking is done to verify if the `fsid` matches what is expected and users no longer get a “failed to probe daemons or devices" error.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-09 17:36:46 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: | 2102272 | ||
|
Comment 4
Sebastian Wagner
2021-11-26 14:18:35 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 |