Bug 1437782

Summary:	Unable to mount with latest gluster builds 3.8.4-19
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	glusterd	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, mchangir, rcyriac, rhinduja, rhs-bugs, sbhaloth, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-20	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:35:56 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:	1417151

Description Vivek Das 2017-03-31 07:45:10 UTC

Description of problem:

I had a 3.2 setup and i upgraded to latest gluster builds i.e 3.8.4-19 when i tried to run mount -a it is throwing error saying mount failed. Even fuse mount is failing.
Everything was going well before updating to latest gluster version.

Version-Release number of selected component (if applicable):
glusterfs-3.8.4-19.el7rhgs.x86_64

How reproducible:


Steps to Reproduce:
1.Update to glusterfs-3.8.4-19.el7rhgs.x86_64
2. try mount -a command or try mounting fuse
3.

Actual results:
Mount fails

Expected results:
Mount should succeed

Additional info:

Comment 3 Atin Mukherjee 2017-03-31 08:27:32 UTC

We are analysing it now.

Comment 10 Vivek Das 2017-03-31 12:47:12 UTC

Updated the system to glusterfs-3.8.4-20 and now mount works.
Hence marking it as verified.

Comment 12 errata-xmlrpc 2017-09-21 04:35:56 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-2017:2774