Bug 1437782 - Unable to mount with latest gluster builds 3.8.4-19
Summary: Unable to mount with latest gluster builds 3.8.4-19
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Pranith Kumar K
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-03-31 07:45 UTC by Vivek Das
Modified: 2017-09-21 04:35 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8.4-20
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:35:56 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

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
Note You need to log in before you can comment on or make changes to this bug.