Blame rhel/systemd/cloud-config.target

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