Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab

[bugproxy]

Problem Description
====================
It seems the remote mounts in my /etc/fstab file are not being automatically mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart scripts not running because they require certain mounts being available. I can give access to the machine via SSH key or password. Using mount -a or any other mount command works just fine after bootup. I don't personally notice a problem in logs with mounts.

The machine is a VM hosted on a Power8 PowerKVM system running:
# uname -a
Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux
# cat /etc/base-release
IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1)

VM details:
# uname -a
Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.10
DISTRIB_CODENAME=utopic
DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"

If I recall correctly, we installed the 141002 daily build of Utopic Unicorn (14.10).

I have implemented a workaround for now. I updated /etc/fstab to use IP addresses instead of names, put "mount -a" as the first non-commented line in /etc/init.d/mountnfs.sh and updated the crontab to run the jobs I had in the upstart configs. This works until the problem is fixed.

---uname output---
Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = ppc64le

Steps to Reproduce
=========================
 Without the workaround implemented and NFS mounts in your /etc/fstab, boot up the machine. It should be evident the mount points aren't there with df -h.

== Comment: #3 - Breno Henrique Leitao <email address hidden> - ==
I was able to reproduce this problem.
NFS is not mounted automatically, but it is when you run 'mount -a'.
I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1389164/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-02-09 08:00 EDT-------
Any updates on this bug ?

[Luciano Chavez (lnx1138)]

I believe 14.10 is no longer in support. Does this problem persist in either Trusty or Xenial?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-05-19 01:58 EDT-------
== Comment from Nicole ==
(In reply to comment #11)
> I believe 14.10 is no longer in support. Does this problem persist in either
> Trusty or Xenial?

I do not believe so. I believe this bug was specific to 14.10 which is now out of service. Thanks!

[Launchpad Janitor (janitor)]

[Expired for mountall (Ubuntu) because there has been no activity for 60 days.]