[Bug 1515446] Re: network file systems in FSTAB no longer mount at boot with NetworkManager

[Bryan Quigley]

Thanks for uploading to dev!

Here is a debdiff for an SRU to wily

** Description changed:

- After a fresh install of 15.10, nfs shares no longer mount on boot.
- I'm using the same line to mount as I did in 14.04 prior:
+ [Impact]
+ 
+  * This breaks NFS mounts coming up reliably.  In some cases this can be
+ quite intermittent.
+ 
+ [Test Case]
+ 
+  1. Add a mountpoint to an NFS share by name to fstab.
+  2. See that it mounts with the mount command.
+  3. Reboot 5+ times, note that it doesn't come up all (or the majority of the time).  
+ 
+ [Regression Potential]
+ 
+  * There could be a regression for the same reason it's blocked in
+ Debian, because of dependency issues with packages not converted to
+ systemd that want to run /etc/rcS.d/.
+ 
+ You can check for this by looking for breaking/disable services during
+ bootup.  Ubuntu is in a much better state than Debian, but there is a
+ possibility we missed something.
+ 
+ Otherwise, this will increase boot time, but when the user logs the
+ networking will be more likely to be ready.
+ 
+ 
+ -Previous description-
+ After a fresh install of 15.10, nfs shares no longer mount on boot.   I'm using the same line to mount as I did in 14.04 prior:
  
  <server>:/share  /mnt/share  ntfs4  _netdev, auto 0 0
  
  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.
  
  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)
  
  lsb_release -rd
  Description:    Ubuntu 15.10
  Release:        15.10
  
  lsb_release -rd
  Description:    Ubuntu 15.10
  Release:        15.10
  bjwest at razorback:~$ apt-cache policy nfs-common
  nfs-common:
-   Installed: 1:1.2.8-9ubuntu10
-   Candidate: 1:1.2.8-9ubuntu10
-   Version table:
+   Installed: 1:1.2.8-9ubuntu10
+   Candidate: 1:1.2.8-9ubuntu10
+   Version table:
  
-  *** 1:1.2.8-9ubuntu10 0
-         500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
-         100 /var/lib/dpkg/status
+  *** 1:1.2.8-9ubuntu10 0
+         500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
+         100 /var/lib/dpkg/status
  
  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
-    Loaded: loaded (/etc/fstab)
-    Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago
-     Where: /mnt/share
-      What: hog:/share
-      Docs: man:fstab(5)
-            man:systemd-fstab-generator(8)
-   Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32)
+    Loaded: loaded (/etc/fstab)
+    Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago
+     Where: /mnt/share
+      What: hog:/share
+      Docs: man:fstab(5)
+            man:systemd-fstab-generator(8)
+   Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32)
  
  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed state.

** Patch added: "network-manager_1.0.4-0ubuntu5.3_wily.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1515446/+attachment/4558670/+files/network-manager_1.0.4-0ubuntu5.3_wily.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1515446

Title:
  network file systems in FSTAB no longer mount at boot with
  NetworkManager

Status in One Hundred Papercuts:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  New

Bug description:
  [Impact]

   * This breaks NFS mounts coming up reliably.  In some cases this can
  be quite intermittent.

  [Test Case]

   1. Add a mountpoint to an NFS share by name to fstab.
   2. See that it mounts with the mount command.
   3. Reboot 5+ times, note that it doesn't come up all (or the majority of the time).  

  [Regression Potential]

   * There could be a regression for the same reason it's blocked in
  Debian, because of dependency issues with packages not converted to
  systemd that want to run /etc/rcS.d/.

  You can check for this by looking for breaking/disable services during
  bootup.  Ubuntu is in a much better state than Debian, but there is a
  possibility we missed something.

  Otherwise, this will increase boot time, but when the user logs the
  networking will be more likely to be ready.

  
  -Previous description-
  After a fresh install of 15.10, nfs shares no longer mount on boot.   I'm using the same line to mount as I did in 14.04 prior:

  <server>:/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:    Ubuntu 15.10
  Release:        15.10

  lsb_release -rd
  Description:    Ubuntu 15.10
  Release:        15.10
  bjwest at razorback:~$ apt-cache policy nfs-common
  nfs-common:
    Installed: 1:1.2.8-9ubuntu10
    Candidate: 1:1.2.8-9ubuntu10
    Version table:

   *** 1:1.2.8-9ubuntu10 0
          500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
          100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
     Loaded: loaded (/etc/fstab)
     Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago
      Where: /mnt/share
       What: hog:/share
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)
    Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1515446/+subscriptions