Refactor #20194: foreman-installer fails with puppetserver from Puppet 5 - Installer - Foreman

Actions

Copy link

Refactor #20194

closed

foreman-installer fails with puppetserver from Puppet 5

Added by Oliver Freyermuth almost 7 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Foreman modules

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/puppet-puppet/pull/515, https://github.com/theforeman/foreman-installer/pull/235

Fixed in Releases:

Found in Releases:

Foreman - Nightly

Red Hat JIRA:

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

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Anonymous almost 7 years ago

Puppet 5 is not supported, yet. (2017-07-08: it's working with all features now)

Actions

Copy link

Updated by Anonymous almost 7 years ago

Related to Refactor #20196: Puppet 5 infra tasks added

Actions

Copy link

Updated by Anonymous almost 7 years ago

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

Actions

Copy link

Updated by Oliver Freyermuth almost 7 years ago

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

Actions

Copy link

Updated by Anonymous almost 7 years ago

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...).

Actions

Copy link

Updated by Oliver Freyermuth almost 7 years ago

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.

Actions

Copy link

Updated by Anonymous almost 7 years ago

It won't get into 1.15.

Actions

Copy link

Updated by Anonymous almost 7 years ago

FWIW, puppet strings (and kafo) is working fine for me after installing the puppet-strings and rgen (https://tickets.puppetlabs.com/browse/PDOC-168) gems.

Actions

Copy link