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. In that case we have: 1) The nbd-client sysvinit service will not work as expected; users will notice and hopefully will find this bug report telling them that they need to revert the $network patch. But now we have: 2) The nbd-client sysvinit service breaking not only itself but other packages as well! Network-manager or other services randomly not starting! This even affects persons that don't use the nbd-client sysvinit service at all, but just need the nbd-client executable (like LTSP or QEMU users or persons wishing to use nbd-client to temporarily access a remote disk). I believe that (2) is a lesser evil than (1), which I imagine only affect a minority of the ubuntu-server installations that also happend to need the nbd-client service. In any case, if this won't be fixed for Xenial, let's please mention it in this bug report, so that we develop a workaround in LTSP, for all LTSP users that need it immediately. Thanks a lot, Alkis -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: Breaking ordering cycle by deleting job nbd-client.service/start Status in nbd package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Won't Fix 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+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
