Description of problem: It has been reported on users that after upgrading hosts to 4.2 / GlusterFS 3.12 NFS support stopped to work. This has an easy workaround which is installing glusterfs-gnfs package. Please ensure nfs over gluster still work after upgrading.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
This would need a spec change to add a dependency on glusterfs-gnfs package. Do we want to install this package on all gluster servers managed by oVirt given that the recommended nfs solution is to use nfs-ganesha?
For glusterfs-3.12 (and 3.13) installing the additional glusterfs-gnfs package is acceptable. However, starting with Gluster 4.0, the package will not be made available anymore, and if NFS is expected to work, NFS-Ganesha will need to be used.
(In reply to Sahina Bose from comment #2) > This would need a spec change to add a dependency on glusterfs-gnfs package. > Do we want to install this package on all gluster servers managed by oVirt > given that the recommended nfs solution is to use nfs-ganesha? I'm fine going with nfs-ganesha provided that at the end of the upgrade NFS over glusterfs which was configured on 4.1 still works
Moved to vdsm since the patch is addressing the dependency there.
Removing blocker for 4.2.1 as there's a workaround to address the issue
Can this move to QE?
Yes
Tested with oVirt 4.2 & gluster-3.12, I could observe that glusterfs-gnfs package is marked as dependency for vdsm
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.