This problem is caused by ipsec-tools's /etc/init.d/setkey having a
header that declares both runlevel S and a dependency on $remote_fs,
which causes a dependency loop:
[ 23.730602] systemd[1]: basic.target: Found ordering cycle on
basic.target/start
[ 23.730606] systemd[1]: basic.target: Found dependency on paths.target/start
[ 23.730607] systemd[1]: basic.target: Found dependency on acpid.path/start
[ 23.730609] systemd[1]: basic.target: Found dependency on
sysinit.target/start
[ 23.730610] systemd[1]: basic.target: Found dependency on
setkey.service/start
[ 23.730612] systemd[1]: basic.target: Found dependency on
remote-fs.target/start
[ 23.730613] systemd[1]: basic.target: Found dependency on
remote-fs-pre.target/start
[ 23.730614] systemd[1]: basic.target: Found dependency on
open-iscsi.service/start
[ 23.730616] systemd[1]: basic.target: Found dependency on
network-online.target/start
[ 23.730617] systemd[1]: basic.target: Found dependency on
network.target/start
[ 23.730619] systemd[1]: basic.target: Found dependency on
NetworkManager.service/start
[ 23.730620] systemd[1]: basic.target: Found dependency on basic.target/start
[ 23.730622] systemd[1]: basic.target: Breaking ordering cycle by deleting
job paths.target/start
(With several other loops to follow)
In 16.04 and later, packages should not use init scripts with runlevel
S, but instead should ship native systemd units to avoid such dependency
problems.
** Changed in: ipsec-tools (Ubuntu)
Importance: Medium => Critical
** Changed in: ipsec-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574833
Title:
setkey is not run automatically on system start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1574833/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
