Bug 1539406

Summary:	the readiness timeout for rhgs-server-container should take into account higher number of bricks
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	cns-deploy-tool	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	cns-3.6	CC:	bmohanra, hchiramm, jarrpa, kramdoss, rcyriac, rgeorge, rhs-bugs, vinug
Target Milestone:	---
Target Release:	CNS 3.6 Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-30 08:36:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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