Description of problem: In glusterfs, nfs component is optional. But in the regression tests, it is not. Version-Release number of selected component (if applicable): master How reproducible: 100% Expected results: Depending on the configure flag, even the tests using nfs should be considering enable/disable. Additional info: Considering in certain usecases, (like brick-mux enabled tests, we don't need nfs, we can save lot of regression time in brick-mux tests in this scenario).
REVIEW: https://review.gluster.org/22010 (tests: run nfs tests only if --enable-gnfs is provided) posted (#2) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/22010 (tests: run nfs tests only if --enable-gnfs is provided) merged (#7) on master by Niels de Vos
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/
REVIEW: https://review.gluster.org/23548 (tests: mark tests/bugs/glusterd/quorum-value-check.t as NFS test) posted (#1) for review on master by Sanju Rakonde
REVIEW: https://review.gluster.org/23548 (tests: mark tests/bugs/glusterd/quorum-value-check.t as NFS test) merged (#2) on master by Atin Mukherjee