Bug 1964570 - Auto deletion of mon canary pod stuck in Terminating state and also not reconciled by the operator, leading to stuck deployment [NEEDINFO]
Summary: Auto deletion of mon canary pod stuck in Terminating state and also not recon...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Travis Nielsen
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-25 18:01 UTC by Neha Berry
Modified: 2023-08-09 17:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-02 15:33:36 UTC
Embargoed:
tnielsen: needinfo? (nberry)

Attachments (Terms of Use)

Comment 3 Travis Nielsen 2021-05-25 19:15:49 UTC 
The Rook operator force deletes the canary pods, with the intention that they will stop as soon as possible and allow the real mon pods to start. This behavior has been the same for several releases, not sure what would have changed. If we cannot repro this, I would suggest it be closed as won't fix. 

If we do see it again, Rook could potentially force delete the mon canaries again if it sees they are stuck terminating for a long time.
Comment 4 Mudit Agarwal 2021-06-03 13:01:14 UTC 
Neha, is this reproducible? Else can we close this? 
https://bugzilla.redhat.com/show_bug.cgi?id=1964570#c3
Comment 6 Mudit Agarwal 2021-06-10 10:06:03 UTC 
Moving out after talking to Neha.
Comment 7 Travis Nielsen 2021-07-26 19:33:15 UTC 
Neha shall we close this or could you get a repro?
Comment 8 Travis Nielsen 2021-08-02 15:33:36 UTC 
Please reopen if you can repro
Note You need to log in before you can comment on or make changes to this bug.