Public bug reported: When running cloud-init with puppet configuration in the user-data a bunch of problems occurs when cloud-init tries install and start puppet:
Problem 1: Enabling of puppet fails cloud-init isn't able to enable the puppet service, because non of the options in _autostart_puppet in cc_puppet.py is valid (see: https://github.com/number5/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L35-L48). For Ubuntu 12.04 LTS /etc/default/puppet was created when installing puppet which caused that issue not to occur there. Problem 2: (Re)Starting of puppet fails I worked around Problem 1, by including the following bootcmd into the userdata: bootcmd: - echo START=yes > /etc/default/puppet Even then puppet doesn't get installed correctly, because when cloud-init tries to start puppet (by using "service puppet start") puppet is already running (because it has been started during the installation) and "service puppet start" is returning 1 as return code, causing cloud-init to fail. Problem 3: puppet is still not enabled Manually restarting puppet works, but puppet won't do anything useful, because: Aug 12 15:41:39 ip-10-128-24-151 puppet-agent[26304]: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations'); Aug 12 15:41:39 ip-10-128-24-151 puppet-agent[26304]: Use 'puppet agent --enable' to re-enable. Please fix those issues to make cloud-init with setup of puppet working again. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1355909 Title: cloud-init with puppet doesn't work in trusty Status in Init scripts for use on cloud images: New Bug description: When running cloud-init with puppet configuration in the user-data a bunch of problems occurs when cloud-init tries install and start puppet: Problem 1: Enabling of puppet fails cloud-init isn't able to enable the puppet service, because non of the options in _autostart_puppet in cc_puppet.py is valid (see: https://github.com/number5/cloud-init/blob/master/cloudinit/config/cc_puppet.py#L35-L48). For Ubuntu 12.04 LTS /etc/default/puppet was created when installing puppet which caused that issue not to occur there. Problem 2: (Re)Starting of puppet fails I worked around Problem 1, by including the following bootcmd into the userdata: bootcmd: - echo START=yes > /etc/default/puppet Even then puppet doesn't get installed correctly, because when cloud-init tries to start puppet (by using "service puppet start") puppet is already running (because it has been started during the installation) and "service puppet start" is returning 1 as return code, causing cloud-init to fail. Problem 3: puppet is still not enabled Manually restarting puppet works, but puppet won't do anything useful, because: Aug 12 15:41:39 ip-10-128-24-151 puppet-agent[26304]: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations'); Aug 12 15:41:39 ip-10-128-24-151 puppet-agent[26304]: Use 'puppet agent --enable' to re-enable. Please fix those issues to make cloud-init with setup of puppet working again. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1355909/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
