diff options
| author | Scott Moser <smoser@brickies.net> | 2016-09-15 09:30:50 -0400 |
|---|---|---|
| committer | Scott Moser <smoser@brickies.net> | 2016-09-15 09:32:28 -0400 |
| commit | 3705bb5964a2ff3f9a67265e6d090a112b35e40c (patch) | |
| tree | c897ed14939860db968f078f6d38f27bd1b4280d /systemd | |
| parent | c099719a3fae3adf5275fd0ab02b7b764cd30381 (diff) | |
| download | vyos-cloud-init-3705bb5964a2ff3f9a67265e6d090a112b35e40c.tar.gz vyos-cloud-init-3705bb5964a2ff3f9a67265e6d090a112b35e40c.zip | |
systemd: put cloud-init.target After multi-user.target
When we moved cloud-final.service to run After multi-user.target it
caused a dependency loop (as cloud-init.target was still implied to be
Before multi-user.target).
journalctl would either show:
cloud-init.target: Breaking ordering cycle by deleting job
cloud-final.service/start
or
multi-user.target: Breaking ordering cycle by deleting job
cloud-init.target/start
The fix here is to clearly state that cloud-init.target is also
After multi-user.target
LP: #1623868
Diffstat (limited to 'systemd')
| -rw-r--r-- | systemd/cloud-init.target | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/cloud-init.target b/systemd/cloud-init.target index a63babb0..d5684582 100644 --- a/systemd/cloud-init.target +++ b/systemd/cloud-init.target @@ -4,3 +4,4 @@ # b.) touch a file /etc/cloud/cloud-init.disabled [Unit] Description=Cloud-init target +After=multi-user.target |