Description of problem: ganesha config files in (/var)/run/gluster/shared_storage/nfs-ganesha need to be marked with %config(noreplace) in the glusterfs-ganesha subpackage. They probably need to be "ghosted" (with %ghost) too Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
POST with rebase to nfs-ganesha-2.5.x
Kaleb, Can you please provide the steps to verify this BZ? What this fix will do? I tested this with 3.4,I could see the ganesha-ha.conf.sample files which is been installed as part of glusterfs-ganesha is present at /etc/ganesha/. Are we expecting these files to be present at shared storage directly as part of package installation? But then again..shared_storage is created post package installation. What is the difference in behaviour from 3.3.1 to RHGS 3.4 wrt to this BZ? Thanks..
After an upgrade from rhgs-3.3.x to 3.4 the ganesha config files in /run/gluster/shared-storage/nfs-ganesha should be saved to, e.g. ganesha.conf.rpmsave. Prior to 3.4 the files could have been over-written. And I don't see that that any change was actually made, so this will likely not pass. ;-)
Thanks Kaleb and Jiffin. Based on comment #8 and comment #10 ..Since the fix for this BZ is not available with the current RHGS 3.4 ganesha build. In order to track this BZ and to get the patch with next ganesha build ...Moving this BZ to assigned 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-2018:2610