Bug 2392390
| Summary: | [7.1z Backport][GSS] MGRs constantly failed over and interfering with upgrade | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bipin Kunal <bkunal> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Sayalee <saraut> |
| Severity: | high | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | adking, akane, cephqe-warriors, mobisht, rpollack, tserlin, vdas |
| Target Milestone: | --- | Flags: | mobisht:
needinfo+
|
| Target Release: | 7.1z8 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-18.2.1-352.el9cp | Doc Type: | Bug Fix |
| Doc Text: |
.cephadm mgr module no longer makes excessive calls to the `list_servers`, alleviating locking issues
Previously, the cephadm mgr module was making excessive calls to the `list_servers` mgr API call. As a result, locking issues occurred within the manager.
With this fix, stray daemon check frequency is now controlled by the new `mgr/cephadm/stray_daemon_check_interval` config option, which defaults to 1800 seconds (30 minutes).
The `list_servers` calls are now significantly reduced, alleviating manager locking issues.
|
Story Points: | --- |
| Clone Of: | 2390032 | Environment: | |
| Last Closed: | 2025-09-30 15:03:24 UTC | Type: | --- |
| 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: | 2390032 | ||
| Bug Blocks: | |||
|
Description
Bipin Kunal
2025-09-01 13:44:13 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 7.1 security and bug fix updates), 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-2025:17059 |