Hide Forgot
Description of problem: Current Puppet Nova-compute configuration forces NFS version 4. This creates performance and scalability issues in basically all modern NFS environment where the standard is 4.1 Since RHEL 7.4, nfs 4.1 is fully supported and default too. https://github.com/openstack/tripleo-heat-templates/blob/stable/queens/puppet/services/nova-compute.yaml#L300 Would be nice to remove the hardcoded "vers=4,nfsvers=4" (BTW it has been written twice) Version-Release number of selected component (if applicable): OSP13, OSP14, OSP15 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This was hard set to 4 to prevent users to use NFSv3 which has locking issues. I agree we should make this configurable where vers can be >=4 and defaults to 4.
so are we not suppose to use NFSv3 , i had a request from user they want to use NFSv3 - is it not supported
(In reply to Anil Dhingra from comment #2) > so are we not suppose to use NFSv3 , i had a request from user they want to > use NFSv3 - is it not supported yes, NFSv3 is not supported due to locking. This has resulted in issues in the past.
(In reply to Martin Schuppert from comment #3) > (In reply to Anil Dhingra from comment #2) > > so are we not suppose to use NFSv3 , i had a request from user they want to > > use NFSv3 - is it not supported > > yes, NFSv3 is not supported due to locking. This has resulted in issues in > the past. One of the issue is https://bugzilla.redhat.com/show_bug.cgi?id=1547095 . Also check https://access.redhat.com/solutions/2780381
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:2811