vyos-cloud-init.git/systemd, branch 20.4

Run cloud-init-local.service after the hv_kvp_daemon (#505)

2020-08-31T15:23:59+00:00

This ensures that KVP data can be correctly reported to Azure.

systemd: add Before=shutdown.target when Conflicts=shutdown.target is used (#546)

2020-08-27T17:16:13+00:00

Lintian spotted the following issue: The specified systemd .service file contains both DefaultDependencies=no and Conflicts=shutdown.target directives without Before=shutdown.target. This can lead to problems during shutdown because the service may linger until the very end of shutdown sequence as nothing requests to stop it before (due to DefaultDependencies=no). There is race condition between stopping units and systemd getting a request to exit the main loop, so it may proceed with shutdown before all pending stop jobs have been processed. Please add Before=shutdown.target. [1] https://lintian.debian.org/tags/systemd-service-file-shutdown-problems.html Co-authored-by: Rick Harding

cloud-init.service.tmpl: use "rhel" instead of "redhat" (#452)

2020-06-23T13:43:04+00:00

We use "rhel" consistently everywhere else.

Change from redhat to rhel in systemd generator tmpl (#450)

2020-06-23T12:41:15+00:00

The name `redhat' is not used but rather `rhel' to identify the distro. Signed-off-by: Eduardo Otubo

cloud-init.service: on centos/fedora/redhat wait on NetworkManager.service

2019-10-31T14:45:29+00:00

In Centos/RHEL 8, NetworkManager is installed as the networking service. cloud-init.service needs to run After this service to allow the OS to bring networking up first. LP: #1843334

systemd/cloud-init.service.tmpl: start after wicked.service

2019-09-26T14:39:27+00:00

Change the startup order. On SUSE distros cloud-init.service should start after wicked.service. This reflects the same start up order other distributions utilize.

cloud-init-generator: use libexec path to ds-identify on redhat systems

2019-06-19T17:16:08+00:00

Update the template to use libexec prefix path to ds-identify on redhat systems. LP: #1833264

systemd: Render generator from template to account for system differences.

2019-01-28T17:51:57+00:00

The systemd generator used had a hard coded path for the location target file to create. This path does not apply to all distributions. Make the generator and template to have the path set during build time.

systemd: On SUSE ensure cloud-init.service runs before wicked

2018-10-24T14:34:50+00:00

With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE Linux Enterprise. This requires that cloud-init.service starts before wicked. LP: #1799709

cloud-config.service: run After snap.seeded.service.

2018-05-14T19:38:22+00:00

This makes cloud-config.service (and as a result cloud-final.service) run After snap.seeded.service. This is required to ensure that pre-seeded snaps can be used by cloud-init or user-data input. The snap.seeded.service was added to snapd at: https://github.com/snapcore/snapd/pull/5124 Note that the following would be a workaround: snap: commands: 00: snap wait system seed.loaded LP: #1767131