Puppet fails with puppet 4

Bug #1446804 reported by Phil Fenstermacher on 2015-04-21
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Romanos Skiadas

Bug Description

cloud-init is incompatible with Puppet 4 (released April 15)

Notable differences:

Package name is puppet-agent (not puppet)
Installed in /opt/puppetlabs/bin/
PUPPET_CONF_PATH = '/etc/puppetlabs/puppet/puppet.conf'
PUPPET_SSL_CERT_DIR = '/etc/puppetlabs/puppet/ssl/certs/'
PUPPET_SSL_DIR = '/etc/puppetlabs/puppet/ssl'
PUPPET_SSL_CERT_PATH = '/etc/puppetlabs/puppet/ssl/certs/ca.pem'

I'm happy to attempt writing a patch, but I'm not sure if this should be a new module or a modification to the existing module.

Related branches

Same issue here. Is there a plan to make cloud-init compatible? The simplest thing seems to make the hard coded constants configurable via the UserData attribute so that the Puppet provisioner knows where to put things and how to access the binary.

james beedy (jamesbeedy) wrote :

Same issue here!

Romanos Skiadas (rski) wrote :

This is getting rather serious, especially given how close puppet 3's EOL date is (About a month).
I looked into it, adding support for puppet 4 would've been pretty straight forward if it weren't for one thing: Some distros do not adhere to the new paths and still use /etc/puppet instead of /etc/puppetlabs, /var instead of /etc/puppetlabs etc.

Romanos Skiadas (rski) wrote :

I've started working on this so I'll assign it to myself.

Changed in cloud-init:
assignee: nobody → Romanos Skiadas (rski)
Romanos Skiadas (rski) on 2016-11-25
Changed in cloud-init:
status: New → In Progress
Robert Heinzmann (reg-x) wrote :

Why not use "puppet config set NAME VALUE --section", which hides implementation from the puppet module.

Just take care that "puppet" is in the path (e.g. /opt/puppetlabs/bin/puppet)

Scott Moser (smoser) on 2017-02-10
Changed in cloud-init:
importance: Undecided → Medium

This bug is believed to be fixed in cloud-init in 18.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers