Bug 1635692

Summary:	upgrade steps should inform users to change value of GLUSTER_BLOCKD_STATUS_PROBE_ENABLE to 1
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	doc-Container_Native_Storage_with_OpenShift	Assignee:	storage-doc
Status:	CLOSED DUPLICATE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	asriram, rhs-bugs, sankarshan, storage-doc
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-03 13:46:12 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:
Bug Depends On:
Bug Blocks:	1629843

Description Raghavendra Talur 2018-10-03 13:42:29 UTC

Description of problem:
rhgs-server pods now have ability to check for the status of gluster-blockd and fail the pod if gluster-blockd is not running. The templates that are shipped in cns-deploy have the check turned off by default.

We should add a step in upgrade documentation asking users change the value for GLUSTER_BLOCKD_STATUS_PROBE_ENABLE to 1 to enable it.

Comment 2 Raghavendra Talur 2018-10-03 13:46:12 UTC


*** This bug has been marked as a duplicate of bug 1635586 ***