Bug 2029697
| Summary: | cepadm-adopt fails when dashboard is enabled | ||
|---|---|---|---|
| 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: | Ameena Suhani S H <amsyedha> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.0 | CC: | aschoen, asriram, ceph-eng-bugs, fkellehe, gabrioux, gmeno, nthomas, sunnagar, tserlin, vereddy, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 5.0z4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-6.0.20.2-1.el8cp | Doc Type: | Known Issue |
| Doc Text: |
.The `cephadm-adopt.yml` playbook currently fails when the dashboard is enabled on the Grafana node
Currently, the `cephadm-adopt.yml` playbook fails to run as it does not create the `/etc/ceph` directory on nodes deployed only with a Ceph monitor.
To work around this issue, manually create the `/etc/ceph` directory on the Ceph monitor node before running the playbook. Verify the directory is owned by the `ceph` user’s UID and GID.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-08 13:01:20 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: | 1959686 | ||
|
Description
Ameena Suhani S H
2021-12-07 05:36:59 UTC
Actual results: adopt playbook failed to adopt to cephadm Expected results: adopt playbook should to adopt to cephadm 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.0 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:0466 |