Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=908123.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-02-05T23:47:21+00:00 John wrote: 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: Reply at: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/0 ------------------------------------------------------------------------ On 2013-02-06T04:42:24+00:00 John wrote: [ 6.943559] systemd[1]: Found ordering cycle on NetworkManager-wait-online.service/start [ 6.943707] systemd[1]: Walked on cycle path to NetworkManager.service/start [ 6.943810] systemd[1]: Walked on cycle path to dbus.socket/start [ 6.943912] systemd[1]: Walked on cycle path to sysinit.target/start [ 6.944039] systemd[1]: Walked on cycle path to local-fs.target/start [ 6.944141] systemd[1]: Walked on cycle path to var-storage-fuse-mp3.mount/start [ 6.944287] systemd[1]: Walked on cycle path to var-storage.mount/start [ 6.944388] systemd[1]: Walked on cycle path to remote-fs-pre.target/start [ 6.944490] systemd[1]: Walked on cycle path to network.target/start [ 6.944588] systemd[1]: Walked on cycle path to NetworkManager-wait-online.service/start [ 6.944735] systemd[1]: Breaking ordering cycle by deleting job NetworkManager.service/start [ 6.944883] systemd[1]: Job NetworkManager.service/start deleted to break ordering cycle starting with NetworkManager-wait-online.service/start [ 6.945103] systemd[1]: Deleting job NetworkManager-wait-online.service/start as dependency of job NetworkManager.service/verify-active Reply at: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/1 ------------------------------------------------------------------------ On 2013-08-04T20:44:30+00:00 Raman wrote: Same problem here during reboot on Fedora 19: Aug 4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to nfs-darwin.mount/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to network.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to NetworkManager.service/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to dbus.socket/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to sysinit.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Breaking ordering cycle by deleting job nfs-darwin.mount/stop Aug 4 16:18:43 edison systemd[1]: Job nfs-darwin.mount/stop deleted to break ordering cycle starting with local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to nfs-darwin-home.mount/stop /etc/fstab contains: darwin:/ /nfs/darwin nfs4 rw,soft,intr,noauto 0 0 Reply at: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/2 ------------------------------------------------------------------------ On 2013-12-09T01:47:35+00:00 Zbigniew wrote: This should be fixed by the latest f18 systemd update. Reply at: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/comments/3 ** Changed in: systemd Status: Unknown => Fix Released ** Changed in: systemd Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in avahi package in Ubuntu: Confirmed Status in nbd package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed 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://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 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.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start 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.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
