Description of problem: Mounting NFSv3 shares in %post kickstart section fails. This breaks our installation procedure. NFSv4 has not been tested. Mounting the share with the same command in the installed Fedora 26 environment works. Version-Release number of selected component (if applicable): # netinstall environment $ uname -r 4.11.0-0.rc3.git0.2.fc26.x86_64 # installed environment $ uname -r 4.11.0-0.rc6.git0.1.fc26.x86_64 How reproducible: easy 100% Steps to Reproduce: 1. start installation of F26 with Fedora-Workstation-netinst-x86_64-26-Alpha-1.7.iso 2. switch with Alt+Tab to console window 3. mounting NFS share will fail with command: mkdir -p /mnt/sysinst mount -v -t nfs -o nolock,vers=3 <IPv4-address>:/install /mnt/sysinst Actual results: mount.nfs: timeout set for Fri Apr 21 07:26:16 2017 mount.nfs: trying text-based options 'nolock,vers=3,addr=<IPv4-address>' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying <IPv4-address> prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying <IPv4-address> prog 100005 vers 3 prot UDP port 635 mount.nfs: mount(2): No such device mount.nfs: No such device Expected results: NFS share should be mounted. Additional info: in Fedora 24 it worked just fine. In installed Fedora 26 system command works too: -bash-4.4# mount -v -t nfs -o nolock,vers=3 <IPv4-address>:/install /mnt/sysinst mount.nfs: timeout set for Fri Apr 21 09:23:03 2017 mount.nfs: trying text-based options 'nolock,vers=3,addr=<IPv4-address>' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying <IPv4-address> prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying <IPv4-address> prog 100005 vers 3 prot UDP port 635 Maybe this is a related bug 1443662?
The problem is still present in Fedora 26 Beta using: Fedora-Workstation-netinst-x86_64-26_Beta-1.4.iso Installing the package 'nfs-utils' does not solve the problem. The command to mout is: # mount -v -t nfs -o nolock,nfsvers=3 <IPv4-address>:/install /mnt/sysinst Its output is: mount.nfs: trying <IPv4-address> prog 100003 vers 3 prot TCP port 2049 mount.nfs: trying <IPv4-address> prog 100005 vers 3 prot UDP port 635 mount.nfs: mount(2): No such device mount.nfs: No such device mount.nfs: timeout set for Fri Jun 16 17:14:49 2017 mount.nfs: trying text-based options 'nfsvers=3,addr=<IPv4-address>' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: prog 100005, trying vers=3, prot=17 Our installation system relies on mounting NFSv3 shares in %post kickstart section.
See bug 1443662#c11 for a workaround.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
From my point of view this is resolved. The command: mount -v -t nfs -o nolock <IPv4-address>:/install /mnt/sysinst successfully mounts NFSv3 share with the latest version of Fedora 26 and its netinstall ISO file. The output is of the above command in %post is: mount.nfs: mount(2): Protocol not supported mount.nfs: mount(2): Protocol not supported mount.nfs: mount(2): Protocol not supported mount.nfs: trying <IPv4-address> prog 100003 vers 3 prot TCP port 2049 mount.nfs: trying <IPv4-address> prog 100005 vers 3 prot UDP port 635 mount.nfs: timeout set for Sat Mar 3 21:45:46 2018 mount.nfs: trying text-based options 'nolock,vers=4.2,addr=<IPv4-address>,clientaddr=<IPv4-address2>' mount.nfs: trying text-based options 'nolock,vers=4,minorversion=1,addr=<IPv4-address>,clientaddr=<IPv4-address2>' mount.nfs: trying text-based options 'nolock,vers=4,addr=<IPv4-address>,clientaddr=<IPv4-address2>' mount.nfs: trying text-based options 'nolock,addr=<IPv4-address>' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: prog 100005, trying vers=3, prot=17 I did not test Fedora 27. I tested Fedora 28 with Fedora-Workstation-netinst-x86_64-28-20180302.n.0.iso and packages from current date of posting. Fedora 28 behaves the same as Fedora 26.