Bug #8134
closed
No enable-puppetlabs-repo in kickstart-katello.erb
Description
We use the parameter "enable-puppetlabs-repo" that is included in the default foreman kickstart file to install the repo.
Currently on a freshly provisioned Centos 7 host there is no puppet installed because the package cannot be found.
I modified the Katello Kickstart default to include:
<% if puppet_enabled && @host.params['enable-puppetlabs-repo'] && @host.params['enable-puppetlabs-repo'] == 'true' -%>
repo --name=puppetlabs-products --baseurl=http://yum.puppetlabs.com/el/<%= @host.operatingsystem.major %>/products/<%= @host.architecture %>
repo --name=puppetlabs-deps --baseurl=http://yum.puppetlabs.com/el/<%= @host.operatingsystem.major %>/dependencies/<%= @host.architecture %>
<% end -%>
Updated by Eric Helms over 10 years ago
- Category set to 83
- Assignee set to Stephen Benjamin
- Triaged changed from No to Yes
Updated by Stephen Benjamin over 10 years ago
I don't think this is really a change I want to see to our templates.
You can clone and customize your kickstart to enable community repos directly, but the expected behavior would be to use Katello to manage all your content -- you can sync yum.puppetlabs.com repos to Katello and hosts can use them to get the agent.
Updated by Eric Helms over 9 years ago
- Status changed from New to Rejected
Setting status based on Stephen's comment and age of the issue without comment. If still feel this should be changed, please re-open..\
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release set to 166