Blame rhel/systemd/cloud-config.target

Packit Service ef27ab
# cloud-init normally emits a "cloud-config" upstart event to inform third
Packit Service ef27ab
# parties that cloud-config is available, which does us no good when we're
Packit Service ef27ab
# using systemd.  cloud-config.target serves as this synchronization point
Packit Service ef27ab
# instead.  Services that would "start on cloud-config" with upstart can
Packit Service ef27ab
# instead use "After=cloud-config.target" and "Wants=cloud-config.target"
Packit Service ef27ab
# as appropriate.
Packit Service ef27ab
Packit Service ef27ab
[Unit]
Packit Service ef27ab
Description=Cloud-config availability
Packit Service ef27ab
Wants=cloud-init-local.service cloud-init.service
Packit Service ef27ab
After=cloud-init-local.service cloud-init.service