[ubuntu 16.10] nfs fstab entry fails to mount on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Impact: NFS shares listed in /etc/fstab do not mount on boot.
During booting, it appears that the nfs share attempts to mount before the network allows for name resolution (see errors below). However, the systemd dependencies clearly show a requirement for network-
Regression potential: This same issue appears to have been addressed in LP: #1515446 but I observe the problem on a fresh install of kubuntu 16.10.
Configuration and error logs:
> tail -2 /etc/fstab
# nfs mounts
zpl-scope:
> systemctl status mnt-scopearray.
● mnt-scopearray.
Loaded: loaded (/etc/fstab; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2016-11-16 15:47:07 CST; 45min ago
Where: /mnt/scopearray
What: zpl-scope:
Docs: man:fstab(5)
Nov 16 15:47:07 zpl-purple systemd[1]: Mounting /mnt/scopearray...
Nov 16 15:47:07 zpl-purple mount[1406]: mount.nfs: Failed to resolve server zpl-scope: Name or ser
Nov 16 15:47:07 zpl-purple systemd[1]: mnt-scopearray.
Nov 16 15:47:07 zpl-purple systemd[1]: Failed to mount /mnt/scopearray.
Nov 16 15:47:07 zpl-purple systemd[1]: mnt-scopearray.
> systemctl list-dependencies mnt-scopearray.
mnt-scopearray.
● ├─-.mount
● ├─system.slice
● └─network-
● ├─networking.
● └─NetworkManage
> lsb_release -rd
Description: Ubuntu 16.10
Release: 16.10
> apt-cache policy network-manager
network-manager:
Installed: 1.2.4-0ubuntu1
Candidate: 1.2.4-0ubuntu1
Version table:
*** 1.2.4-0ubuntu1 500
500 http://
100 /var/lib/
> apt-cache policy nfs-common
nfs-common:
Installed: 1:1.2.8-9.2ubuntu1
Candidate: 1:1.2.8-9.2ubuntu1
Version table:
*** 1:1.2.8-9.2ubuntu1 500
500 http://
100 /var/lib/
Mitigation / workaround: Adding 'x-systemd.