** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Breaking ordering cycle by deleting job nbd-client.service/start
+ metabug: Breaking ordering cycle by deleting job NetworkManager.service/start
** Summary changed:
- metabug: Breaking orderin
Got this bug again other Ubuntu 16.04.3 LTS system:
$ journalctl | grep -i network
ноя 06 22:49:57 norbert-vaio kernel: FUJITSU Extended Socket Network Device
Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Found ordering cycle
o
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avahi (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/1487679
Title:
CRIT
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: util-linux (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/1487679
Title:
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/1487679
Title:
CR
** Also affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** 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/b
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/1487679
Title:
Hi Martin,
I don't have access to any systems without network-manager (that's
ubuntu-server installations, I imagine?) so I cannot say if it currently
works with plain ifupdown or not, and if the patch will break it.
Let's assume the worst, that it now works there and that the patch will
break it
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487679
Title:
Breaking ordering cycle by deleting job nbd-client.service/start
To manage notifications about this bug go to:
http
@Alkis: Doesn't that break nbd-client for people who use ifupdown? With
that patch it will start much earlier, way before the network is up.
Does nbd-client get along with that? I. e. it doesn't fail on startup
without a network connection and listens for new network connections
coming up?
** No
@pitti, since
1) wouter isn't planning to fix this upstream soonish (Debian freeze is months
ahead),
2) the issue is serious, i.e. people that install nbd-client, then randomly
don't have network-manager running after reboots,
3) the included patch is surely better than the existing situation, i.
** 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/1487679
Title:
Breaking ordering cycle by deleting job nbd-client.service/
I confirm that by enabling NetworkManager-wait-online.service in Debian
Stretch, I started getting dependency cycles.
Replacing "# Default-Start: S" with "# Default-Start: 2 3 4 5" didn't solve
the cycles.
Any fixes or workarounds for Xenial?
For now, I removed "Required start: $network" from
+Before=network.target
This is absolutely necessary too, otherwise NetworkManager can be
stopped (on shutdown/reboot) before services that require the network to
be up get shut down. Thus these services often hang then.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
The main difference between D and U is that Debian's NetworkManager does
not enable NetworkManager-wait-online.service by default. This is very
likely to create an ordering cycle like this, as this pulls in
NetworkManager (which is late boot) into network-online.target, which
nbd-client requires.
I was able to reproduce the issue in Debian Stretch after applying an
Ubuntu specific patch to it. So I'm suspecting that Ubuntu's etwork-
manager might be involved in this, I've put it to the affects list.
Specifically, by editing Debian's /lib/systemd/system/NetworkManager.service
like this:
-A
I can't reproduce the issue in Debian Stretch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487679
Title:
Breaking ordering cycle by deleting job nbd-client.service/start
To manage notifications
Hmm. The "2 3 4 5" change doesn't seem to be enough to break the
dependency cycle.
I played a bit to see what could break the cycle but I couldn't find it.
By completely removing /etc/init.d/nbd-client, all is fine.
By putting *just* this minimal header:
# Required-Start: $network
...and removin
The same issue (mostly) was reported in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=796633
Wouter plans to replace the init script with a generator in time for
Debian Stretch.
I've asked him to comment on if what pitti suggested is acceptable till
then (for Ubuntu Xenial's release).
** Bu
This is indeed a too strong/impossible (with NetworkManager) requirement
in /etc/init.d/nbd-client:
# Required-Start: $network $local_fs
# Default-Start: S
A service can't simultaneously run in early boot *and* require the
network to be up, as that does not work with NetworkManager, connman, or
s
I'm experiencing this in Xenial 16.04 fully updated.
I have nbd-client installed but I'm not using its sysvinit service at all
(LTSP).
One out of 10 boots, systemd decides to:
Απρ 07 08:20:15 srv1-dide systemd[1]: network.target: Breaking ordering cycle
by deleting job NetworkManager.service/star
I have this problem as well, or at least a related one. On my system
systemd resolves the cycle by disabling NetworkManager, so I have no
internet until I systemctl start NetworkManager. Here's the relevant
section of the log:
Feb 04 12:17:32 Behemoth systemd[1]: network-online.target: Found order
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nbd (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/1487679
Title:
Breaki
23 matches
Mail list logo
