Vivid and Wily fixes uploaded.
** Changed in: setserial (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: setserial (Ubuntu Vivid)
Status: Triaged => In Progress
** Description changed:
NFSd does not start due to systemd ordering cycle.
Manually starting with "systemctl start nfs-kernel-server" after boot
works fine.
here systemd lines from dmesg:
[ 43.569341] systemd[1]: Cannot add dependency job for unit
gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file
or directory.
[ 43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start
[ 43.620748] systemd[1]: Found dependency on network.target/start
[ 43.646476] systemd[1]: Found dependency on NetworkManager.service/start
[ 43.672292] systemd[1]: Found dependency on basic.target/start
[ 43.697952] systemd[1]: Found dependency on sockets.target/start
[ 43.723381] systemd[1]: Found dependency on cups.socket/start
[ 43.748530] systemd[1]: Found dependency on sysinit.target/start
[ 43.773533] systemd[1]: Found dependency on setserial.service/start
[ 43.798185] systemd[1]: Found dependency on remote-fs.target/start
[ 43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start
[ 43.871768] systemd[1]: Found dependency on nfs-server.service/start
[ 43.896442] systemd[1]: Breaking ordering cycle by deleting job
network.target/start
[ 43.921641] systemd[1]: Job network.target/start deleted to break ordering
cycle starting with nfs-server.service/start
SRU test case
=============
- - Install network-manager, nfs-kernel-server, and setserial into a clean
vivid VM.
- - Reboot, and you'll find the above ordering cycle (check "sudo journalctl
-p warning"). "systemctl status nfs-server.service" will be not running (it
could also be that the cycle gets broken on a different point, but that's the
most likely one).
- - With the fixed setserial package (upgrade, then reboot) there should be no
cycle and all services start up normally.
+ - Install network-manager, nfs-kernel-server, and setserial into a clean
vivid VM.
+ - Reboot, and you'll find the above ordering cycle (check "sudo journalctl
-p warning"). "systemctl status nfs-server.service" will be not running (it
could also be that the cycle gets broken on a different point, but that's the
most likely one).
+ - With the fixed setserial package (upgrade, then reboot) there should be no
cycle and all services start up normally.
+ - Double-check "systemctl status setserial" that the unit started and output
from the init.d script looks reasonable.
+
+ Regression potential: The new .service has less strict startup
+ dependencies/ordering than the autogenerated LSB one, so I don't see a
+ potential problem with introducing new cycles. The new unit could
+ potentially fail to start if there's a bug in unit installation (this is
+ covered by the test case). So all in all, very low.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1
Uname: Linux 4.1.0-040100rc1-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 7 12:26:09 2015
InstallationDate: Installed on 2012-12-22 (865 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to setserial in Ubuntu.
https://bugs.launchpad.net/bugs/1452644
Title:
NFSd does not start due to systemd ordering cycle with setserial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1452644/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
