Bug 2209493
| Summary: | Observing health error on cluster due to "Module 'cephadm' has failed" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Pawan <pdhiran> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Mohit Bisht <mobisht> |
| Severity: | medium | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | adking, akraj, cephqe-warriors, mobisht, saraut, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 6.1z1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-17.2.6-84.el9cp | Doc Type: | Bug Fix |
| Doc Text: |
.Error-handling is updated to work with the python version used in {storage-product} 6.1
Previously, a new timeout on `cephadm` commands added in {storage-product} 6.1 would not work correctly due to a python version difference affecting the type of error generated. Due to this, whenever one of these timeouts actually happened, the generated error was not handled and the `cephadm` module would crash.
With this fix, the error-handling is updated to work with the python version used in {storage-product} 6.1. When one of these timeouts occurs, it results in a health warning about what timed out, and the `cephadm` module no longer crashes.
|
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
Pawan
2023-05-24 03:42:46 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 |