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
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
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