Breaking ordering cycle by deleting job NetworkManager.service/start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
High
|
|||
avahi (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
nbd (Debian) |
Fix Released
|
Unknown
|
|||
nbd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Triaged
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
nfs-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
rpcbind (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
util-linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
$ apt-cache policy nbd-client
nbd-client:
Installed: 1:3.8-4ubuntu0.1
Candidate: 1:3.8-4ubuntu0.1
Version table:
*** 1:3.8-4ubuntu0.1 0
500 http://
500 http://
100 /var/lib/
1:3.8-4 0
500 http://
I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following:
Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.
Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.
Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.
Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated.
-------
Bug with NFS-server and RPC-bind is indicated by messages:
$ journalctl | grep -i break
ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.
ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.
ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.
ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.
tags: | added: patch |
summary: |
- Breaking ordering cycle by deleting job nbd-client.service/start + metabug: Breaking ordering cycle by deleting job + NetworkManager.service/start |
summary: |
- metabug: Breaking ordering cycle by deleting job + CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start |
tags: | added: xenial |
description: | updated |
Changed in systemd: | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
Changed in nbd (Debian): | |
status: | Unknown → Fix Released |
no longer affects: | shorewall (Ubuntu) |
no longer affects: | shorewall (Ubuntu Xenial) |
no longer affects: | ipsec-tools (Ubuntu Xenial) |
no longer affects: | ipsec-tools (Ubuntu) |
no longer affects: | shorewall6 (Ubuntu Xenial) |
no longer affects: | shorewall6 (Ubuntu) |
no longer affects: | cloud-initramfs-tools (Ubuntu) |
no longer affects: | cloud-initramfs-tools (Ubuntu Xenial) |
no longer affects: | open-iscsi (Ubuntu Xenial) |
no longer affects: | open-iscsi (Ubuntu) |
no longer affects: | cloud-init (Ubuntu) |
no longer affects: | cloud-init (Ubuntu Xenial) |
no longer affects: | xe-guest-utilities (Ubuntu Xenial) |
no longer affects: | xe-guest-utilities (Ubuntu) |
no longer affects: | aoetools (Ubuntu Xenial) |
no longer affects: | aoetools (Ubuntu) |
Changed in systemd (Ubuntu Xenial): | |
status: | Confirmed → New |
Description of problem:
With NFS mounts in an fstab it appears that NetworkManager and the autogenerated mount units get into a dependency loop which causes a number of important units to get discarded while trying to resolve the issue.
Version-Release number of selected component (if applicable):
Seen in FC16,17,18
How reproducible:
Every boot with NFS mounts in the fstab
Steps to Reproduce:
1. Try and boot a system with NFS mounts in the fstab.
2.
3.
Actual results:
Several units are deleted and never attempt to stop, several others fail because the root filesystem doesn't get remounted RW until other units time out.
Expected results:
System should come up, remount the root filesystem RW, mount NFS volumes in the fstab without dependency loops or units timing out.
Additional info: