Bug 1734534

Summary:	Upgrading a RHGS node fails when user edited glusterd.vol file exists
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	amukherj, bmekala, rhs-bugs, sheggodu, storage-qa-internal, vbellur, vdas
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-12	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1737676 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:22:40 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:	1737676
Bug Blocks:	1696809, 1729027

Description Raghavendra Talur 2019-07-30 19:36:43 UTC

Description of problem:
When a user had edited the glusterd.vol file in /etc/glusterfs and updates the glusterfs packages, bricks cannot contact glusterd.

Version-Release number of selected component (if applicable):
RHGS 3.5.0


How reproducible:
Always

Steps to Reproduce:
1. install glusterfs
2. create and start a volume
3. edit glusterd.vol and add a custom option
4. yum update gluster packages
5. restart volumes

Comment 13 errata-xmlrpc 2019-10-30 12:22:40 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/RHEA-2019:3249