Bug 2120598 - [GSS] [4.11.z-Clone] ceph cluster unresponsive when 2 nodes of same zone is down in stretch cluster
Summary: [GSS] [4.11.z-Clone] ceph cluster unresponsive when 2 nodes of same zone is d...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ODF 4.11.1
Assignee: Travis Nielsen
QA Contact: Mahesh Shetty
URL:
Whiteboard:
Depends On: 2113062 2120601
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-23 11:25 UTC by Sunil Kumar Acharya
Modified: 2023-08-09 17:03 UTC (History)
23 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, two MONs could end up on the same node instead of being spread across unique nodes. This happened when the operator was restarted in the middle of a MON failover, multiple MONs could be started on the same node, which reduced the MON quorum availability. With this update, the operator properly cancels the MON failover if the MON failover times out, and ensures that any extra MONs are removed based on the stretch topology or multiple MONs that run on the same node.
Clone Of: 2113062
Environment:
Last Closed: 2022-09-14 15:15:05 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 405 0 None open Bug 2120598: mon: Improve mon failover reliability [4.11] 2022-08-25 18:53:58 UTC
Github rook rook pull 10717 0 None open mon: Improve mon failover reliability to better handle failure and topology 2022-08-23 11:28:52 UTC
Red Hat Product Errata RHBA-2022:6525 0 None None None 2022-09-14 15:15:25 UTC

Comment 16 errata-xmlrpc 2022-09-14 15:15:05 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 OpenShift Data Foundation 4.11.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-2022:6525
Note You need to log in before you can comment on or make changes to this bug.