Bug 2161083 - Cluster Object Store is in unhealthy state for more than 15s. Please check Ceph cluster health.
Summary: Cluster Object Store is in unhealthy state for more than 15s. Please check Ce...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Blaine Gardner
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-15 17:55 UTC by bmcmurra
Modified: 2023-08-09 17:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-07 14:23:09 UTC
Embargoed:


Attachments (Terms of Use)

Comment 3 Nitin Goyal 2023-01-16 04:14:26 UTC
Moving it to the rook.

Comment 7 Blaine Gardner 2023-01-23 19:13:02 UTC
I thought that 4.9 still had the uninstall/reinstall bug where the rook operator pod needs to be restarted to fix this. Try restarting the rook operator pod to see if the issue resolves itself.

Comment 12 Blaine Gardner 2023-03-07 15:31:55 UTC
The customer could also disable the health checks for the ObjectStore. That will also remove the readiness probe from the RGW, but if there is only one, that shouldn't be an issue. Backporting this to 4.9 will prove to be a bit of a challenge, and too many competing priorities keep coming up.

Comment 13 Blaine Gardner 2023-03-14 15:25:54 UTC
Forgot needinfo last week

Comment 15 Travis Nielsen 2023-04-04 15:28:54 UTC
After further discussion, backporting it will be difficult with other related rgw readiness probe issues. 
Blaine, to what release have we already backported the bucket health check disabling? If that's sufficient, please close it.

Comment 16 Blaine Gardner 2023-04-04 15:46:48 UTC
Right. I believe ODF 4.10 has a number of additional patches, and I believe this issue should not be possible there. In 4.13, the health check routine is removed entirely after hearing concerns from the RGW team.


Note You need to log in before you can comment on or make changes to this bug.