Bug 2126566 - [GSS][rook] core: increase liveness probe timeout to 5s
Summary: [GSS][rook] core: increase liveness probe timeout to 5s
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.10
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
: ODF 4.12.0
Assignee: Travis Nielsen
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-13 22:11 UTC by Randy Martinez
Modified: 2023-08-09 17:03 UTC (History)
8 users (show)

Fixed In Version: 4.12.0-80
Doc Type: Bug Fix
Doc Text:
Cause: Ceph daemon liveness probe may be too short Consequence: Stability issues have been observed with a liveness probe timeout of 1s. Fix: Increase the liveness probe timeout to 5s Result: More stable Ceph daemon pods.
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 422 0 None open Bug 2126566: Increase liveness probe timeout to 5s 2022-10-17 18:49:33 UTC
Github rook rook pull 10986 0 None open core: increase liveness probe timeout to 5s 2022-09-13 22:42:36 UTC

Comment 7 Elad 2022-10-27 07:10:50 UTC
Hi Travis,

Anything special to test here for validating the fix?

Comment 8 Travis Nielsen 2022-10-27 15:19:36 UTC
(In reply to Elad from comment #7)
> Hi Travis,
> 
> Anything special to test here for validating the fix?

A simple analysis of the liveness probe to see its timeout is 5s on the pod is sufficient, thanks

Comment 11 Prasad Desala 2022-11-16 08:39:51 UTC
Verified this BZ on ODF version: 4.12.0-113

      livenessProbe:
        exec:
        ...
        failureThreshold: 3
        initialDelaySeconds: 10
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 5

Liveness probe timeout for ceph pods{osd,mgr,mon. mds} is now set to 5sec.


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