Bug 2005515 - Ceph mgr pod sometimes stuck in init state after node drain during machineconfig update
Summary: Ceph mgr pod sometimes stuck in init state after node drain during machinecon...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: rook
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.7.5
Assignee: Travis Nielsen
QA Contact: Itzhak
URL:
Whiteboard:
Depends On: 1990031
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-17 20:57 UTC by Travis Nielsen
Modified: 2021-10-26 19:51 UTC (History)
15 users (show)

Fixed In Version: v4.7.5-246.ci
Doc Type: If docs needed, set a value
Doc Text:
Previously, when the nodes restarted, the MGR pod got stuck in a pod initialisation state which resulted in the inability to create new persistent volumes (PVs). With this update, the MGR pod restarts even if the MONs are down.
Clone Of: 1990031
Environment:
Last Closed: 2021-10-26 19:51:34 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift rook pull 288 0 None open Bug 2005515: Add timeout in mgr init container 2021-10-05 07:34:19 UTC
Red Hat Product Errata RHBA-2021:4002 0 None None None 2021-10-26 19:51:39 UTC

Comment 3 Mudit Agarwal 2021-10-08 07:54:07 UTC 
Please add doc text
Comment 4 Travis Nielsen 2021-10-08 16:20:15 UTC 
Doc text added
Comment 9 Elad 2021-10-17 09:03:06 UTC 
Moving to VERIRIED based on the verification done for this bug over OCS 4.6.8 - https://bugzilla.redhat.com/show_bug.cgi?id=1990031#c30
Comment 12 Itzhak 2021-10-20 14:53:09 UTC 
The text seems fine. The mgr pod will restart even if we mons are down.
Comment 17 errata-xmlrpc 2021-10-26 19:51:34 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 Container Storage 4.7.5 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-2021:4002
Note You need to log in before you can comment on or make changes to this bug.