Thanks for bisecting to the change you need already - that is great! But it seems we need something more to recreate and verify the fix eventually.
Per your last comment I have set my autofs config to: testmount -vers=4.0 -fstype=nfs,rw,retry=0 192.168.122.55:/export/users/testmount Which is using your -vers=4.0 string that you have shown At least after an autofs reload it still worked. Then I restarted the system to make sure it only knows about the new vers=4.0 config. But it still works and mounts it as 4.0 Here from mount output: 192.168.122.55:/export/users/testmount on /nfs/testmount type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.226,local_lock=none,addr=192.168.122.55) That is using autofs in Cosmic as you reported: autofs 5.1.2-4ubuntu1 nfs-common 1:1.3.4-2.2ubuntu3 Do you happen to know what we still miss to trigger it for my repro? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
