PuppetThreeWorkarounds¶

• Table of contents
• PuppetThreeWorkarounds
  • Status
  • Fixed issues
  • Remaining issues
    • Proxy complains of autosign permissions issues
• Conclusions

This page details the various fixes for making Foreman work with Puppet 3. If your issue is not listed, please open a bug report on the issue tracker, and detail appropriate workarounds (with link to the bug number) here.

Status¶

Currently Foreman 1.1 (unreleased) works reliably with Puppet 3. This is available either from the nightly packages (.deb or RPM) or from git (develop branch), with updates to both the Foreman UI and the Smart Proxy.

Fixed issues¶

The develop branch contains fixes for the following issues:

• uninitialized constant HostObserver (#1872)
• could not find value for $confdir (Puppet::Settings::InterpolationError)
• report processing seems to work but the summaries are all zero
• cannot view certificates that are present on the proxy
  • ensure sudo rules allow access to /usr/bin/puppet now instead of /usr/sbin/puppetca (foreman-installer has already been updated)
• cannot import classes, "Attempting to initialize global default settings more than once!"

Remaining issues¶

Proxy complains of autosign permissions issues¶

The current version of Puppet ignores the file permissions settings in puppet.conf. In other words, this doesn't work:

[master]
      autosign       = /etc/puppet/autosign.conf { mode = 664 }

However, for the moment, it's so broken that puppet will not fix the ownership of the file, so you can run this instead:

chown foreman-proxy:puppet /etc/puppet/autosign.conf

Alternatively, you could try moving it to the [main] section of the puppet.conf, which also seems to fix the problem.

Logged with patch as Puppet issue #17371.

Conclusions¶

There may well be other problems too. Let us know on the bug tracker, IRC, or the dev mailing list if you find any.