Bug 2075510
| Summary: | [Cephadm]: cephadm does not display the recreated osd | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Ameena Suhani S H <amsyedha> |
| Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | high | ||
| Version: | 5.0 | CC: | adking, akraj, aschoen, ceph-eng-bugs, gabrioux, gmeno, msaini, nthomas, tserlin, vereddy, ykaul |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 5.1z2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-6.0.25.7-1.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.Removal of legacy directory ensures error-free cluster post adoption
Previously, `cephadm` displayed an unexpected behaviour with its 'config inferring' function whenever a legacy directory, such as `/var/lib/ceph/mon` was found. Due to this behaviour, post adoption, the cluster was left with the following error "CEPHADM_REFRESH_FAILED: failed to probe daemons or devices".
With this release, the adoption playbook ensures the removal of this directory and the cluster is not left in an error state after the adoption.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-30 20:54:48 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: | 2099589 | ||
|
Comment 6
Ameena Suhani S H
2022-04-14 15:37:17 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 5.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-2022:5450 |