Bug 1724449 - Ganesha: add dependency for var-run-gluster-shared_storage.mount
Summary: Ganesha: add dependency for var-run-gluster-shared_storage.mount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.5.0
Assignee: Jiffin
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1696809
TreeView+ depends on / blocked
 
Reported: 2019-06-27 06:56 UTC by Jiffin
Modified: 2019-10-30 12:15 UTC (History)
11 users (show)

Fixed In Version: nfs-ganesha-2.7.3-7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:15:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3252 0 None None None 2019-10-30 12:15:56 UTC

Description Jiffin 2019-06-27 06:56:33 UTC 
Description of problem:

The ganesha has a dependency on shared storage. There was a downstream-only patch for resolving this issue in past 3.x release. It got slipped in the release.

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

How reproducible:
always

Steps to Reproduce:
1. Reboot the server

Actual results:
Sometimes ganesha fails to start

Expected results:
Ganesha should start after reboot

Additional info:
http://pkgs.devel.redhat.com/cgit/rpms/nfs-ganesha/plain/0003-Restart-nfs-ganesha-service-post-reboot.patch?h=rhgs-3.4.4-rhel-7 ---> 3.4 patch
Comment 1 Jiffin 2019-07-08 11:44:10 UTC 
will address in next update
Comment 5 Manisha Saini 2019-08-26 03:13:32 UTC 
Verified this BZ -

# rpm -qa | grep ganesha
nfs-ganesha-2.7.3-7.el7rhgs.x86_64
glusterfs-ganesha-6.0-11.el7rhgs.x86_64
nfs-ganesha-gluster-2.7.3-7.el7rhgs.x86_64

Rebooted one of the server node.Ganesha service got started when the node came up.
Moving this BZ to verified state
Comment 7 errata-xmlrpc 2019-10-30 12:15:39 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:3252
Note You need to log in before you can comment on or make changes to this bug.