Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2256453

Summary: [RHCS 6.x clone] Ceph MGR repeatedly goes unresponsive requiring a restart
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Manny <mcaldeir>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED ERRATA QA Contact: Mohit Bisht <mobisht>
Severity: high Docs Contact: Disha Walvekar <dwalveka>
Priority: unspecified    
Version: 6.1CC: adking, bhubbard, ceph-eng-bugs, cephqe-warriors, dwalveka, gfarnum, mcaldeir, mobisht, nojha, tserlin, vereddy, vumrao
Target Milestone: ---   
Target Release: 6.1z4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-17.2.6-173.el9cp Doc Type: Bug Fix
Doc Text:
Cause: cephadm maintains a list of known upgrade failure reasons, but a bug in the code was causing the last two items to not actually be included in that list. Consequence: If the upgrade were to fail for one of those last two reasons, most notably in the case of an offline host, the cephadm mgr module would crash Fix: The list of potential upgrade failure issues has been repaired. Result: The cephadm mgr module should no longer crash due to upgrade failures.
Story Points: ---
Clone Of: 2253078 Environment:
Last Closed: 2024-02-08 18:11:45 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: 2253078    
Bug Blocks: 2261930    

Comment 10 errata-xmlrpc 2024-02-08 18:11:45 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-2024:0747