touch-packages team mailing list archive

[andrew bezella <abezella@xxxxxxxxxxx>]

Public bug reported:

i'm uncertain exactly when this issue started as we use cfengine
(verifies all expected mounts in place, manually mounts those that are
not).  from a note i have i believe it goes back as far as lucid.

the symptom is that an /etc/fstab entry for an nfs-mounted /home is not
mounted during the system boot. once the system is network-accessible,
manually running `mount -tnfs -av` as root (or using cfengine or any
number of other solutions) is sufficient.

per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be:
mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mountall 2.53
ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
Uname: Linux 3.13.0-38.65-generic x86_64
.run.mount.utab:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Wed Oct 22 16:35:47 2014
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mountall (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions