Bug 1709963
| Summary: | mounting a nonexistent exports give the wrong error | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Steve Dickson <steved> | |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> | |
| Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 8.0 | CC: | bfields, extras-qa, jlayton, steved, swhiteho, xzhou, yoyang | |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
|
| Target Release: | 8.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | bakeathon | |||
| Fixed In Version: | nfs-utils-2.3.3-24.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1709961 | |||
| : | 1752329 (view as bug list) | Environment: | ||
| Last Closed: | 2019-11-05 22:18:26 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: | ||||
| Bug Depends On: | 1709961 | |||
| Bug Blocks: | ||||
|
Description
Steve Dickson
2019-05-14 16:18:51 UTC
We already have testcase to cover this scenario. But the given error message is different: (In reply to Steve Dickson from comment #0) > ... > mount server:/badexportdir /mnt/tmp fails with > mount.nfs: Network is unreachable > > The mount should fail with > mount.nfs: mounting server:/badexportdir failed, reason given by server: No such file or directory > [root@ ~]# exportfs -v /export_test <world>(sync,wdelay,hide,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) [root@ ~]# mount $HOSTNAME:/not_exist/ /mnt/ mount.nfs: access denied by server while mounting hp-dl380pg8-09.rhts.eng.pek2.redhat.com:/not_exist/ ^^^^^^^^^^^^^^^ [root@ ~]# rpm -q nfs-utils nfs-utils-2.3.3-14.el8_0.x86_64 Will update the existing testcase according to this bug fix. I assume from the other bug mentioned in the opening comment that we have a fix for this... is there any reason why this cannot be posted in that case? It looks like another one which should be fairly easy to fix. Have verified in nfs-utils-2.3.3-24.el8
---------------------------------------
[22:03:57 root@ ~~]# timeLimitRun 180 mount 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure.log)
mount.nfs: mounting 127.0.0.1:/notexistdir failed, reason given by server: No such file or directory
^^^^^^^^^^^^^^^^^^^^^^^^^
[22:03:57 root@ ~~]# timeLimitRun 180 mount -t nfs -o vers=3 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure_v3.log)
mount.nfs: access denied by server while mounting 127.0.0.1:/notexistdir
[22:03:58 root@ ~~]# timeLimitRun 180 mount -t nfs4 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure_v4.log)
mount.nfs4: mounting 127.0.0.1:/notexistdir failed, reason given by server: No such file or directory
[22:03:58 root@ ~~]# diff <(cut -d' ' -f2- failure.log) <(cut -d' ' -f2- failure_v4.log)
Compared with nfs-utils-2.3.3-23.el8
---------------------------------------
[22:03:22 root@ ~~]# timeLimitRun 180 mount 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure.log)
mount.nfs: access denied by server while mounting 127.0.0.1:/notexistdir
^^^^^^^^^^^^
[22:03:23 root@ ~~]# timeLimitRun 180 mount -t nfs -o vers=3 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure_v3.log)
mount.nfs: access denied by server while mounting 127.0.0.1:/notexistdir
[22:03:23 root@ ~~]# timeLimitRun 180 mount -t nfs4 127.0.0.1:/notexistdir /mnt/nfsmp &> >(tee failure_v4.log)
mount.nfs4: mounting 127.0.0.1:/notexistdir failed, reason given by server: No such file or directory
[22:03:23 root@ ~~]# diff <(cut -d' ' -f2- failure.log) <(cut -d' ' -f2- failure_v4.log)
1c1
< access denied by server while mounting 127.0.0.1:/notexistdir
---
> mounting 127.0.0.1:/notexistdir failed, reason given by server: No such file or directory
^^^^^^ FAIL - Should use original v4 failure in fall_back cases
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-2019:3579 |