Refactor #20194
closed
foreman-installer fails with puppetserver from Puppet 5
Added by Oliver Freyermuth almost 7 years ago.
Updated almost 7 years ago.
Description
Running foreman-installer on a Foreman machine / smart proxy running PuppetServer from the Puppet 5 distribution results in the exception:
puppetserver[8326]: Exception in thread "main" java.lang.IllegalArgumentException: service :puppetlabs.trapperkeeper.services.metrics.metrics-service/metrics-webservice does not appear in configuration
on puppetserver startup, effectively preventing puppetserver startup.
Seems like the configuration files have been borked.
This hack fixes it:
mv /etc/puppetlabs/puppetserver/conf.d /etc/puppetlabs/puppetserver/conf.d.old
yum reinstall puppetserver
References #15096
Puppet 5 is not supported, yet. (2017-07-08: it's working with all features now)
- Tracker changed from Bug to Refactor
- Project changed from Foreman to Installer
- Category set to Foreman modules
- Status changed from New to Ready For Testing
- Assignee set to Anonymous
- Pull request https://github.com/theforeman/puppet-puppet/pull/515 added
That patch was fast! Please excuse my ignorance - the PR seems to be for "puppet-puppet". Is that puppet-module also what foreman installer is using inside naturally?
In case the testing request is for me: What's the easiest way to get a nightly including the PR (or should I just wait for now)?
Cheers and many thanks,
Oliver
It is the puppet module included with foreman-installer. Use "nightly" instead of "1.15" for the Foreman repositories, than you can apply the patch of the PR to /usr/share/foreman-installer/modules/puppet
Before running the installer for the first time, make sure the "puppet strings" face works, this will probably require to install some gems into the Puppet Ruby environment, see https://github.com/puppetlabs/puppet-strings
It might be well the case that more changes in other Foreman components will be required to get everything working in all setups and there's no timeline for that (just to adjust the expectations...).
Sadly, after this foreman-installer also complains about kafo:
/usr/share/gems/gems/kafo-2.0.0/lib/kafo/puppet_module.rb:69:in `parse': No Puppet module parser is installed and no cache of the file /usr/share/foreman-installer/modules/puppet/manifests/init.pp is available. Please check debug logs and install optional dependencies for the parser. (Kafo::ParserError)
Maybe it's easier to have this (seemingly non-breaking) change in the next point release, i.e. 1.15.2, and not only the 1.16-nightlies, or does this violate release policies?
Since foreman appears to run just fine (apart from the environment filter bug) with puppet5 apart from this, this would get the "fix" to the end-user faster.
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Pull request https://github.com/theforeman/foreman-installer/pull/235 added
Also available in: Atom
PDF
Updated by Anonymous 
Updated by 
Updated by