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:
To answer my own question, I created a dirty fix by creating a new
systemd service that just calls systemctl start setkey.
--
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
Hello,
I there any workaround for this issue?
--
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
** Changed in: ipsec-tools (Ubuntu)
Importance: Undecided => Medium
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ipsec-tools (Ubuntu)
Status: New => Confirmed
--
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:
** No longer affects: systemd (Ubuntu)
--
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:
