Comment 18 for bug 1771382

Just removing the generator leads to cloud-init services not being run at startup on my SLES 12 SP 3 VM with

slestemplate:~ # find /etc/systemd | grep cloud
/etc/systemd/system/cloud-init.target.wants
/etc/systemd/system/cloud-init.target.wants/cloud-final.service
/etc/systemd/system/cloud-init.target.wants/cloud-config.service
/etc/systemd/system/cloud-init.target.wants/cloud-init-local.service
/etc/systemd/system/cloud-init.target.wants/cloud-init.service

All services are enabled according to systemctl status SERVICE

slestemplate:~ # rpm -qa | grep cloud-init
cloud-init-config-suse-18.2-3.1.x86_64
cloud-init-18.2-3.1.x86_64

slestemplate:~ # systemctl status cloud-init.target
● cloud-init.target - Cloud-init target
   Loaded: loaded (/usr/lib/systemd/system/cloud-init.target; static; vendor preset: disabled)
   Active: inactive (dead)
slestemplate:~ # systemctl status cloud-config.target
● cloud-config.target - Cloud-config availability
   Loaded: loaded (/usr/lib/systemd/system/cloud-config.target; static; vendor preset: disabled)
   Active: inactive (dead)

The output I get is:

slestemplate:~ # systemctl |grep cloud

When I do:

slestemplate:~ # systemctl start cloud-init.target
slestemplate:~ # systemctl | grep cloud
cloud-config.service loaded active exited Apply the settings specified in cloud-config
cloud-final.service loaded active exited Execute cloud user/final scripts
cloud-init-local.service loaded active exited Initial cloud-init job (pre-networking)
cloud-init.service loaded active exited Initial cloud-init job (metadata service crawler)
cloud-config.target loaded active active Cloud-config availability
cloud-init.target loaded active active Cloud-init target

So it is still not working out of the box. I enabled all services and the targets with systemctl enable. It is not obvious for me to enable cloud init in case the Systemd generator does not do it. I thought I did, but apparently I did not.