Bug 2207480
Summary: | [CEE/SD][cephadm]Getting the logs "cephadm [INF] Refuse to add /dev/XXX due to limit policy of <xx>" continuously | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Geo Jose <gjose> |
Component: | Cephadm | Assignee: | Adam King <adking> |
Status: | CLOSED ERRATA | QA Contact: | Mohit Bisht <mobisht> |
Severity: | medium | Docs Contact: | Akash Raj <akraj> |
Priority: | unspecified | ||
Version: | 5.3 | CC: | adking, akraj, cephqe-warriors, mobisht, prprakas, saraut, tserlin, vereddy |
Target Milestone: | --- | ||
Target Release: | 6.1z1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ceph-17.2.6-84.el9cp | Doc Type: | Bug Fix |
Doc Text: |
.Message about the limit policy is lowered to debug-level
Previously, `cephadm` would log about hitting the limit policy of an OSD specification at info-level. Due to this, every time the limit policy was hit, `cephadm` would check if any new OSDs should be deployed to match the specification, resulting in the logs to be spammed with messages about hitting the limit.
With this fix, the message about the limit policy is lowered to debug-level and the logs are no longer spammed with messages about limit policy unless they set the log level to debug.
|
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
Geo Jose
2023-05-16 05:14:21 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 |