touch-packages team mailing list archive

[Launchpad Bug Tracker <1391296@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu1.1

---------------
nfs-utils (1:1.2.8-9ubuntu1.1) utopic; urgency=medium

  * debian/nfs-common.statd.upstart: wait for rpcbind job instead of
    relying on portmap compatibility event. (LP: #1391296)
 -- Marc Deslauriers <marc.deslauriers@xxxxxxxxxx>   Tue, 18 Nov 2014 19:07:15 -0500

** Changed in: nfs-utils (Ubuntu Utopic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1391296

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in nfs-utils package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Confirmed
Status in nfs-utils source package in Utopic:
  Fix Released
Status in upstart source package in Utopic:
  Confirmed
Status in nfs-utils source package in Vivid:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  [SRU Request]

  Due to a change in Upstart behaviour, the statd daemon no longer
  starts automatically at boot, resulting in nfs mounts not being
  mounted at boot.

  This has been corrected by modifying the statd upstart job to wait for
  the rpcbind job to start, instead of waiting for the compatibility
  portmap event.

  [Test Case]
  1- set up an NFS mount in /etc/fstab
  2- Reboot, notice the directory didn't get mounted
  3- Install update
  4- Reboot, notice the directory is mounted

  [Regression Potential]
  The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour.

  
  Original description: 

  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions