With the following two bootcmds restarting puppet by cloud-init works (if "apt_upgrade: true" isn't enabled, because that would cause an overwriting of the changes in cc_puppet.py):
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Starting Puppet client version 3.4.3
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations');
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Use 'puppet agent --enable' to re-enable.
I added a patch which should solve the enabling problem. A proper solution inside of cloud-init for the restart would be appreciated too.
With the following two bootcmds restarting puppet by cloud-init works (if "apt_upgrade: true" isn't enabled, because that would cause an overwriting of the changes in cc_puppet.py):
bootcmd: /'restart' /" /usr/lib/ python2. 7/dist- packages/ cloudinit/ config/ cc_puppet. py
- echo START=yes > /etc/default/puppet
- sed -i "s/'start'
But: Puppet is still disabled.
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Starting Puppet client version 3.4.3
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations');
Aug 14 12:52:39 ip-10-128-26-184 puppet-agent[2316]: Use 'puppet agent --enable' to re-enable.
I added a patch which should solve the enabling problem. A proper solution inside of cloud-init for the restart would be appreciated too.