Bug 1686710
| Summary: | [GSS] ceph-medic check failing for ceph cluster running inside container | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Prashant Dhange <pdhange> |
| Component: | Ceph-Medic | Assignee: | Andrew Schoen <aschoen> |
| Status: | CLOSED ERRATA | QA Contact: | Madhavi Kasturi <mkasturi> |
| Severity: | medium | Docs Contact: | Aron Gunn <agunn> |
| Priority: | medium | ||
| Version: | 3.2 | CC: | agunn, aschoen, ceph-qe-bugs, gmeno, tchandra, tserlin |
| Target Milestone: | rc | Flags: | pdhange:
automate_bug?
|
| Target Release: | 4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-medic-1.0.5-1.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.`ceph-medic` can check the health of Ceph running in containers
With this release, the `ceph-medic` utility can now check the health of a {storage-product} cluster running within a container.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 12:45:38 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: | 1730176 | ||
|
Comment 3
Alfredo Deza
2019-03-08 13:17:48 UTC
The upstream commit where this is improved/fixed is: https://github.com/ceph/ceph-medic/commit/84b6c765f6e17038c8ab2527ee825715640d97f9 Maybe the patch can be applied to see if it helps? Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri I've updated the doc text which indicates this is an enhancement. More detailed docs about this are in upstream: https://docs.ceph.com/ceph-medic/master/#inventory-for-containers 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, 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-2020:0312 |