system-config/playbooks/roles/zuul-executor
Jeremy Stanley 8da9b9086f Start zuul-executor after afsd and /afs is mounted
Add an override to the systemd configuration for the docker service
unit so that it won't start until after openafs-client is started
and /afs is mounted (the latter because we don't know if the
initscript will possibly return early). Without this, it's a race to
see whether the container will have a working /afs mount, so can
lead to jobs failing to write into AFS with cryptic permissions
errors.

Change-Id: Ie00b1c1bc9c330e2af28c59b3b07a7c244c912dc
2020-07-27 18:47:52 +00:00
..
defaults Run zuul-executor using docker 2020-06-09 14:26:38 -05:00
files Start zuul-executor after afsd and /afs is mounted 2020-07-27 18:47:52 +00:00
tasks Start zuul-executor after afsd and /afs is mounted 2020-07-27 18:47:52 +00:00
templates Test zuul-executor on focal 2020-05-06 18:00:29 -05:00
vars Run zuul-executor using docker 2020-06-09 14:26:38 -05:00
README.rst Run Zuul using Ansible and Containers 2020-04-24 09:18:44 -05:00

Run Zuul Executor