Bug 1458504
| Summary: | mount.nfs: NFSv4 specified mount need to start negotiation with v4.1 the same as the default NFS mount protocol | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Yongcheng Yang <yoyang> |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | bfields, eguan, jiyin, steved, swhiteho, tlavigne, yoyang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-utils-1.3.0-0.48.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 19:50:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 14
Yongcheng Yang
2017-06-16 03:11:27 UTC
Change back to ON_QA since I found a bug in the nfsmount.conf was being processed. It the upcoming build -48 fixes the problem of setting Defaultvers=4.0 /etc/nfsmount.conf. The problem is the mount is trying 4.1 not 4.0 (In reply to Steve Dickson from comment #16) > It the upcoming build -48 fixes the problem of setting Defaultvers=4.0 > /etc/nfsmount.conf. The problem is the mount is trying 4.1 not 4.0 Thanks for your reminder! Have verified this problem is already fixed in nfs-utils-1.3.0-0.48.el7. Moving to VERIFIED again. ### Reproduced on version -47 ### ----------------------------------------------------------------------------- [root@ ~]# rpm -q nfs-utils nfs-utils-1.3.0-0.47.el7.x86_64 [root@ ~]# grep ^[^#] /etc/nfsmount.conf [ NFSMount_Global_Options ] Defaultvers=4.0 [root@ ~]# mount 127.0.0.1:/export_test/ /mnt/mnt_test/ -vvv mount.nfs: timeout set for Mon Jun 19 21:53:58 2017 mount.nfs: trying text-based options 'vers=4.1,addr=127.0.0.1,clientaddr=127.0.0.1' [root@ ~]# nfsstat -m /mnt/mnt_test from 127.0.0.1:/export_test Flags: rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,local_lock=none,addr=127.0.0.1 [root@ ~]# umount /mnt/mnt_test/ ### Verified on version -48 ### ----------------------------------------------------------------------------- [root@ ~]# rpm -Uvh nfs-utils-1.3.0-0.48.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:nfs-utils-1:1.3.0-0.48.el7 ################################# [ 50%] Cleaning up / removing... 2:nfs-utils-1:1.3.0-0.47.el7 ################################# [100%] [root@ ~]# rpm -q nfs-utils nfs-utils-1.3.0-0.48.el7.x86_64 [root@ ~]# grep ^[^#] /etc/nfsmount.conf [ NFSMount_Global_Options ] Defaultvers=4.0 [root@ ~]# mount 127.0.0.1:/export_test/ /mnt/mnt_test/ -vvv mount.nfs: timeout set for Mon Jun 19 21:54:27 2017 mount.nfs: trying text-based options 'vers=4.0,addr=127.0.0.1,clientaddr=127.0.0.1' [root@ ~]# nfsstat -m /mnt/mnt_test from 127.0.0.1:/export_test Flags: rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,local_lock=none,addr=127.0.0.1 [root@ ~]# umount /mnt/mnt_test/ Will upate testcase to cover this issue now. 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/RHBA-2017:2233 |