0

Due to my manifests requiring the latest version of factor, all provisioned machines has to undergo a manual in-between step after OS installation of adding the puppetlabs repo and upgrading facter.

Even specifying that all subclasses require the installation, it aborts the entire manifest. All 100% after installing latest facter though.

Any way to have the puppetlabs repo being part of the provisioning process? I though uncommenting this line:
<% if puppet_enabled && @host.params['enable-puppetlabs-repo'] && @host.params['enable-puppetlabs-repo'] == 'true' -%> would do the trick, but no.

Also, the variables in the provisioning template (like hte enable-puppetlabs-repo above), where are they set?

Chris Pitman
  • 12,990
  • 3
  • 41
  • 56
Werner
  • 791
  • 1
  • 6
  • 23

1 Answers1

0

This gets applied in foreman's host groups. add it as a parameter to your hostgroup config in the UI and should work.

Adam
  • 1