Details
-
Bug
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
4.5.0
-
None
-
DevOps: Sprint 103
-
FOLIO DevOps
Description
Overview:
After installing the latest (v20.X) Docker Engine Debian package, systemd reports on startup:
Dec 10 16:26:38 vagrant kernel: [ 35.548047] systemd[1]: multi-user.target: Found ordering cycle on okapi.service/start
Dec 10 16:26:38 vagrant kernel: [ 35.548055] systemd[1]: multi-user.target: Job okapi.service/start deleted to break ordering cycle starting with multi-user.target/start
This appears to be because the Docker Engine systemd service now specifies:
After=network-online.target firewalld.service containerd.service multi-user.target
But systemd calculates the dependencies for Okapi as:
vagrant@vagrant:~$ sudo systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After okapi.service Requires=system.slice -.mount sysinit.target Requisite= Wants=docker.service postgresql.service BindsTo= PartOf= Before=shutdown.target multi-user.target After=-.mount system.slice network-online.target postgresql.service docker.service systemd-journald.socket sysinit.target basic.target
Since Okapi is before multi-user.target and after docker.service, while Docker Engine is after multi-user.target, Okapi can't be started by systemd on boot.
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-2907 Okapi service doesn't start on boot in Vagrant VMs
-
- Closed
-