PuppetThreeWorkarounds¶

• Table of contents
• PuppetThreeWorkarounds
  • Status
  • Fixed issues
  • Remaining issues
    • Proxy complains of autosign permissions issues
    • #1997: facts not importing (unconfirmed)

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 (release candidate) works reliably with Puppet 3. Ensure you update both the Foreman UI and the Smart Proxy.

• Foreman 1.1 RC .debs
• Foreman 1.1 RC RPMs

If you hit any other issues, please let us know on the bug tracker, IRC, or the mailing lists.

Fixed issues¶

The develop branch contains fixes for the following issues:

• uninitialized constant HostObserver (#1872)
• could not find value for $confdir (Puppet::Settings::InterpolationError) (#1915)
• report processing seems to work but the summaries are all zero (#1872)
• 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!" (#1915, #1950)
• proxy :puppet_conf setting required (#1983)
• :puppetconfdir setting required (#1994)
• $vardir interpolation problems (#1994)

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.

#1997: facts not importing (unconfirmed)¶

Issue #1997 reports MySQL errors while importing facts, e.g.

Started POST "/fact_values/create" for xxxxxxxx at Wed Dec 05 16:01:05 +0800 2012
Processing by FactValuesController#create as
Parameters: {"facts"=>"[FILTERED]"}
Failed to import facts: Mysql2::Error: Column 'name' cannot be null: ...