Bug 1874866
| Summary: | [GSS][MGR] Module 'pg_autoscaler' has failed: 'op' | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Prashant Dhange <pdhange> |
| Component: | Ceph-Mgr Plugins | Assignee: | Prashant Dhange <pdhange> |
| Status: | CLOSED ERRATA | QA Contact: | Pawan <pdhiran> |
| Severity: | high | Docs Contact: | Ranjini M N <rmandyam> |
| Priority: | high | ||
| Version: | 4.1 | CC: | anharris, bniver, branto, ceph-eng-bugs, ceph-qe-bugs, gsitlani, kdreyer, mmanjuna, mmuench, nojha, pdhiran, rmandyam, tserlin, vereddy |
| Target Milestone: | --- | Flags: | pdhange:
automate_bug?
rmandyam: needinfo+ |
| Target Release: | 5.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.0.0-5535.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.The `pg_autoscaler` module no longer reports failed op error
Previously, the `pg-autoscaler` module reported KeyError for `op` when trying to get the pool status if any pool had the CRUSH rule `step set_chooseleaf_vary_r 1`. As a result, the Ceph cluster health displayed HEALTH_ERR with `Module ’pg_autoscaler’ has failed: op` error.
With this release,only steps with `op` are iterated for a CRUSH rule while getting the pool status and the `pg_autoscaler` module no longer reports the failed `op` error.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-30 08:26:28 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 | ||
|
Comment 6
Prashant Dhange
2020-10-05 00:58:18 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.0 bug fix and enhancement), 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-2021:3294 |