** Branch linked: lp:~network-manager/network-manager/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
network file systems in FSTAB no longer mount at boot with
NetworkManager
Hey Bryan,
thanks for investigating and the patch! Indeed it seems the enabling in
debian/rules got reverted in some merge. The patch is good, except that
I changed postinst to
-if dpkg --compare-versions "$2" lt-nl "0.9.10.0-4ubuntu10"; then
+if dpkg --compare-versions "$2"
** Bug watch added: Debian Bug tracker #812209
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812209
** Also affects: network-manager (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812209
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: network-manager (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage
This should do it properly now on upgrade.. Just readd the blurb that
says it enables it in postinst that actually disabled it..
** Patch added: "network-manager_1.0.4-0ubuntu8.debdiff"
It's disabled explicitly in the rules.
Also in network-manager.postinst it seems that causes it to be disabled as well
in my test.
** Patch added: "network-manager_1.0.4-0ubuntu8.debdiff"
Unfortunately my patch only makes it enabled on a fresh install of
network-manager (or after a purge).It (the upgrade) tries to make
have the services respect if the user changed them starting. Do we care
for network-manager's services? If you don't want them you should have
the package
The attachment "network-manager_1.0.4-0ubuntu8.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
So is that a regression from bug 1430280, perhaps this got inadvertently
dropped in a merge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
** Package changed: nfs-utils (Ubuntu) => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage notifications
Oops - It is related to network-manager.. or more precisely it works
fine if you specify to use dhcp in /etc/network/interfaces. If you
leave it blank (and network-manager actually does the work) then you
have the failures.
--
You received this bug notification because you are a member of
Currently, my testing has not found a specific package that is the cause
(ignore network-manager comment above)
Start with Ubuntu-desktop - it won't mount reliably. Remove packages like
unity, still fails...
Start with Ubuntu-server - it works every time. Install ubuntu-desktop meta
That's not quite correct. The mount initially fails but then it appears
to try again. In any case it does appear end up mounted in Debian.
This also fails on an install without Network-manager on Ubuntu. Will
retry over many restarts on Debian just to confirm.
--
You received this bug
This is not an issue in Debian stretch. Same systemd version, newer network
manager version.
Debian does not have anything defined (on fs) in network-online.target. I
tried removing all of the network-online.target.wants but that hasn't helped
(the only meaningful difference I've found so
Confirming on Lubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage notifications about this bug go to:
To be clear, Fedora does not have this problem in 23 or Rawhide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage notifications
I looked at what Fedora was doing. The only difference seems to be
network-online waits for Networkmanager to say it's online.
sudo systemctl add-wants network-online.target
NetworkManager-wait-online.service
This fixes the issue in my testing. Unfortunately it also makes
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in:
I've been able to work around the problem by adding
'x-systemd.automount,' to the list of options on the fstab line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB
@mtd0, adding that to my fstab worked as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage notifications about this bug go
The x-systemd.automout option works for me as well running 15.10.
Interestingly, it was commented out in my fstab. I believe I tried
that option on 15.04, and it didn't work then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Workaround seems good. Adding 'x-systemd.automount' to fstab mounts NFS
shares during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
This bug has not been tagged before as 'wily' and unfortunately I have
created a duplicate bug report of this one, not being able to find it
earlier.
A few more observations from my original bug report:
It looks like the network is not up when the mounting is done however
systemd dependencies as
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage notifications about this bug go to:
I'm seeing this behavior as well on a fresh install of Xubuntu 15.10.
http://askubuntu.com/questions/689515/mount-network-share-automatically-
on-startup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nfs-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
Opening a task on systemd as well for this.
When called early in boot, mount.nfs may fail because of any number of
problems with the network. In this case, it appears it's being called
by systemd before /etc/resolv.conf has been set up, resulting in a
temporary DNS failure. There is no way for
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515446
Title:
NFS shares in FSTAB no longer mount at boot
To manage
29 matches
Mail list logo
