Bug 1942171
| Summary: | [GSS][Mon][Health-Check] mon_pg_warn_max_object_skew needs lower bound implemented | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Randy Martinez <r.martinez> |
| Component: | RADOS | Assignee: | Christopher Hoffman <choffman> |
| Status: | CLOSED ERRATA | QA Contact: | skanta |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 4.2 | CC: | akraj, akupczyk, bhubbard, ceph-eng-bugs, choffman, gjose, kdreyer, mhackett, mmuench, ngangadh, nojha, pdhiran, r.martinez, rzarzyns, sseshasa, vereddy, vumrao |
| Target Milestone: | --- | Keywords: | Rebase |
| Target Release: | 5.2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.8-2.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.`MANY_OBJECTS_PER_PG` warning is no longer reported when `pg_autoscale_mode` is set to `on`.
Previously, Ceph health warning `MANY_OBJECTS_PER_PG` was reported in instances where `pg_autoscale_mode` was set to `on` with no distinction between the different modes that reported the health warning.
With this release, a check is added to omit reporting `MANY_OBJECTS_PER_PG` warning when `pg_autoscale_mode` is set to `on`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-09 17:35:53 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: | 2102272 | ||
|
Comment 2
Randy Martinez
2021-03-25 01:45:18 UTC
*** Bug 2018117 has been marked as a duplicate of this bug. *** 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 (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement 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/RHSA-2022:5997 |