** Changed in: nfs-utils (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
** Changed in: nfs-utils (Ubuntu Bionic)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
** Changed in: nfs-utils (Ubuntu Focal)
Assignee: Sergio Durigan Junior (sergiodj) =>
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: nfs-utils (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've also rejected this for Groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and network online
To manage notifications about this bug
(and posted wrong bug: mine is https://bugs.launchpad.net/ubuntu/+source
/nfs-utils/+bug/1927745)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name
... and mine* is a pure bugfix ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and network online
To manage notifications about this bug
Guys, this has been sitting in unapproved for about 2 months now, and I
need to push another fix for nfs-utils asap (see
https://bugs.launchpad.net/bugs/1918141). I only noticed this unapproved
upload when I was about to push the git tag, as the upload doesn't show
up in rmadison's output.
I
> I'm not sure it's *ever* correct for distribution packaging to ship
After=network-online.target
you're correct, it's not. As you pointed out that upstream systemd
recommends, what applications *should* do is handle interface
configuration changes (e.g. carrier loss/gain), but few applications
For nfs-server and the risk of applying the fix to stable releases, this
is my take:
It won't break anything unless you've done something truly esoteric, and
then you're on your own anyway IMHO.
It will enable nfs-server to consistently start in configurations using
static addressing, which is
> This isn't a Ubuntu decision - upstream of the package/functionality
goes this way, so if challenged one should challenge it there.
I disagree. This is entirely a question of how we integrate between
services. The distribution is where that integration happens, and users
expect consistency of
For this I honestly see no risks of regressions for nfs-server.
Also, be aware that on systems using DHCP depending on network.target or
network-online.target has the same effect simply due to the inherent
ordering of DHCP packets not passing through until the interface is able
to pass traffic.
Hi Robie - I remember the old discussions and the tag, In this
particular case I think it is somewhat special because.
a) This isn't a Ubuntu decision - upstream of the package/functionality
goes this way, so if challenged one should challenge it there. So if we
want to we should do it there.
b)
I'm not sure it's *ever* correct for distribution packaging to ship
After=network-online.target. One person's "wait for the network to come
online" is another person's "my system hangs on boot because I'm booting
offline" and yet another person's "one NIC was up but the one through
which DNS is
Alternatively, if this is an exceptional case for which the upstream
recommendation shouldn't apply, this should be clearly documented.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and network online
To manage notifications about this
This bug was fixed in the package nfs-utils - 1:1.3.4-4ubuntu2
---
nfs-utils (1:1.3.4-4ubuntu2) hirsute; urgency=medium
* Depend on network-online.target when starting services. (LP: #1918141)
- d/p/lp1918141-use-network-online-target-01.patch: Declare a
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/399744
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/399747
** Merge proposal linked:
** Description changed:
+ [ Impact ]
+
+ nfs-server.service (part of the nfs-utils package) has insufficient
+ dependencies to start correctly in a setting where the NFS exports list
+ contains DNS hostnames (not in local hosts file) or netgroups served via
+ network (for example sssd).
+
+
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/399688
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name
Thanks Niklas, I was able to reproduce the bug here. I'm working on
fixing the service file and will post MPs soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and network online
To manage notifications about this bug go
Ugh, the nfs-utils in Debian/Ubuntu is so incredibly old.
The service file(s) should be updated as they already have upstream, e.g.:
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=blob;f=systemd/nfs-server.service;h=b432f9102d0c50061890b511de1d61069f435991;hb=refs/heads/master
the important
OK, getting the network delay got a little bit convoluted as you can't
clear dependencies with overrides but instead have to copy the unit file
and edit it.
I'm no systemd expert so this can probably be improved, but on a focal
VM host of ours (KVM/Ganeti) that uses systemd-networkd I needed to
First off, nfs-server starts but doesn't export the unresolvable hosts.
The failures do show in systemctl status nfs-server.
To reproduce in a VM you'll likely need something that causes
network.target to be fulfilled but actual network traffic to not be
forwarded until a few seconds later when
Thanks for the report and the great description.
The rationale here makes sense to me, and I agree with updating the
packages in order to solve the described issue. However, since we will
have to SRU this into Focal and Bionic (and I've just noticed that
Hirsute's nfs-server.service file is
I should note that we have observed this on both 18.04LTS (bionic) and
20.04LTS (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and
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/1918141
Title:
27 matches
Mail list logo
