Bug 1539406 - the readiness timeout for rhgs-server-container should take into account higher number of bricks
Summary: the readiness timeout for rhgs-server-container should take into account high...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-deploy-tool
Version: cns-3.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: CNS 3.6 Async
Assignee: Raghavendra Talur
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-28 17:21 UTC by Raghavendra Talur
Modified: 2019-02-13 09:33 UTC (History)
8 users (show)

Fixed In Version: cns-deploy-5.0.0-59.el7rhgs
Doc Type: Bug Fix
Doc Text:
Earlier, in environments with many logical volumes, the rhgs-server-container image did not start within the "failureThreshold" and "periodSeconds" value as configured in the templates. With this fix, the "failureThreshold" value is increased from 15 to 50 in the templates to resolve the issue.
Clone Of:
Environment:
Last Closed: 2018-01-30 08:36:36 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0234 0 normal SHIPPED_LIVE cns-deploy-tool bug fix update 2018-01-30 13:37:03 UTC

Description Raghavendra Talur 2018-01-28 17:21:19 UTC 
Description of problem:
Although the current timeout values work for most of the cases, in setups where there are many bricks and contention at the LVM layer the timeouts might not be sufficient. Hence increase the timeouts in the template files.
Comment 5 Rachael 2018-01-29 12:53:09 UTC 
The new build with rhgs-server-rhel7:3.3.1-3 has the following timeout values:

       readinessProbe:
            timeoutSeconds: 3
            initialDelaySeconds: 40
            exec:
              command:
              - "/bin/bash"
              - "-c"
              - systemctl status glusterd.service
            periodSeconds: 25
            successThreshold: 1
            failureThreshold: 50
          livenessProbe:
            timeoutSeconds: 3
            initialDelaySeconds: 40
            exec:
              command:
              - "/bin/bash"
              - "-c"
              - systemctl status glusterd.service
            periodSeconds: 25
            successThreshold: 1
            failureThreshold: 50

Hence moving the bug to verified
Comment 8 errata-xmlrpc 2018-01-30 08:36:36 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, 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-2018:0234
Note You need to log in before you can comment on or make changes to this bug.