open-iscsi init script creates dependency cycle with NetworkManager
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| open-iscsi (Ubuntu) |
High
|
Unassigned | |||
Bug Description
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on NetworkManager-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Breaking ordering cycle by deleting job NetworkManager-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Job NetworkManager-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on NetworkManager.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Breaking ordering cycle by deleting job NetworkManager.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Job NetworkManager.
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Found dependency on NetworkManager-
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Found dependency on NetworkManager-
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Reached target Network.
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Starting Network.
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Reached target Network is Online.
Jun 15 09:46:55 djledkov-mobl1 systemd[1]: Starting Network is Online.
Jun 15 09:46:56 djledkov-mobl1 whoopsie[1065]: [09:46:56] Could not get the Network Manager state:
Jun 15 09:46:56 djledkov-mobl1 whoopsie[1065]: [09:46:56] GDBus.Error:
So, my system boots, but without any internets =(
| Martin Pitt (pitti) wrote : | #1 |
| affects: | network-manager (Ubuntu) → open-iscsi (Ubuntu) |
| Changed in open-iscsi (Ubuntu): | |
| status: | New → Triaged |
| no longer affects: | systemd (Ubuntu) |
| tags: | added: systemd-boot |
| summary: |
- NetworkManager-wait-online job deleted to break ordering cycle + open-iscsi init script creates dependency cycle with NetworkManager |
| Changed in open-iscsi (Ubuntu): | |
| importance: | Undecided → Critical |
| importance: | Critical → Medium |
| Vincent Ladeuil (vila) wrote : | #2 |
I ran into that bug again now that I really need open-iscsi ;)
I'm using systemd on vivid.
I want to mount remote disks but I don't want to boot from one.
s/remote_
Purging open-iscsi (and removing the mount from fstab) was the only escape path.
I'd try to reproduce on a test system but any advice on what I can try next warmly welcome ;)
| Vincent Ladeuil (vila) wrote : | #3 |
https:/
How far is ubuntu from debian on this precise topic ?
| Vincent Ladeuil (vila) wrote : | #4 |
For the record, on a wily system, there is still a dependency loop involving open-iscsi but system can still boot successfully.
Roughly, I can do:
# apt-get install open-iscsi
# iscsi_discovery <iscsi server IP>
and see the expected volumes
But rebooting from there causes the dependency loop and open-iscsi is not started on next reboot.
I'll try to reproduce in a vm to provide better info.
| Julian Taylor (jtaylor) wrote : | #5 |
still the case in xenial, bumping to high as ending up with no network can be highly problematic.
| Changed in open-iscsi (Ubuntu): | |
| importance: | Medium → High |
| ChristianEhrhardt (paelzer) wrote : | #6 |
There was a merge and it would be great if one could verify if the issue still exists with >2.0.873+
It seems that upload missed jtaylors last test by just a few hours.
Currently we have 2.0.873+
Please if still an issue share what version you had tested and if possible a few simplified steps how to test it to give us a chance to get this fixed before or early in the 16.04 cycle.
| Julian Taylor (jtaylor) wrote : | #7 |
I have rebooted the machine a couple times since and it has not occurred again. Probably the issue has been fixed.
Please reopen if you are still affected.
| Changed in open-iscsi (Ubuntu): | |
| status: | Triaged → Fix Released |
| Mathias Lehnfeld (esqilin) wrote : | #8 |
Occurs consistently on my Xubuntu 16.04 installation. It did infrequently until a few days ago (I don't know exactly).
[ 14.850019] systemd[1]: network-
[ 14.850024] systemd[1]: network-
[ 14.850027] systemd[1]: network-
[ 14.850029] systemd[1]: network-
[ 14.850030] systemd[1]: network-
[ 14.850032] systemd[1]: network-
[ 14.850033] systemd[1]: network-
[ 14.850035] systemd[1]: network-
[ 14.850037] systemd[1]: network-
[ 14.850039] systemd[1]: NetworkManager-
[ 14.850092] systemd[1]: network.target: Found ordering cycle on network.
[ 14.850094] systemd[1]: network.target: Found dependency on NetworkManager.
[ 14.850096] systemd[1]: network.target: Found dependency on basic.target/start
[ 14.850098] systemd[1]: network.target: Found dependency on sockets.
[ 14.850099] systemd[1]: network.target: Found dependency on acpid.socket/start
[ 14.850101] systemd[1]: network.target: Found dependency on sysinit.
[ 14.850102] systemd[1]: network.target: Found dependency on open-iscsi.
[ 14.850104] systemd[1]: network.target: Found dependency on network-
[ 14.850105] systemd[1]: network.target: Found dependency on network.
[ 14.850107] systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.
[ 14.850109] systemd[1]: NetworkManager.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found ordering cycle on network-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on NetworkManager-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on basic.target/start
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on sockets.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on cups.socket/start
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on sysinit.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on open-iscsi.
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Found dependency on network-
Jun 15 09:46:54 djledkov-mobl1 systemd[1]: Breaking ordering cycle by deleting job NetworkManager-
Same old story -- rcS early boot init script with an overly demanding $remote_fs dependency. That can't work together with NetworkManager. Best solution would be to either move this to $local_fs or provide a proper systemd unit with more fine-grained dependencies.