Actions
Bug #17617
closedContent view publishing puppet modules to wrong directory
Difficulty:
Triaged:
Bugzilla link:
Description
I installed a system with Katello 3.2 and puppet 3.8. Shortly afterwords, I ran the foreman-installer -S katello --upgrade-puppet and expected everything to just work. When I published a content view with puppet modules in it, it is still deploying the puppet modules to /etc/puppet/environments instead of the new directory /etc/puppetlabs/code/environments
Updated by Justin Sherrill about 8 years ago
- Has duplicate Bug #18436: Puppet 4 upgrade does not change pulp's puppet_content_dir setting added
Updated by Eric Helms about 8 years ago
- Status changed from New to Assigned
- Assignee changed from Justin Sherrill to Eric Helms
- Translation missing: en.field_release set to 219
Updated by Eric Helms about 8 years ago
- Has duplicate Bug #18131: foreman-installer --upgrade-puppet fails to set new paths for foreman-installer added
Updated by The Foreman Bot about 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/Katello/katello-installer/pull/486 added
Updated by The Foreman Bot about 8 years ago
- Pull request https://github.com/Katello/katello/pull/6651 added
Updated by Eric Helms about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Updated by The Foreman Bot about 8 years ago
- Pull request https://github.com/Katello/katello-installer/pull/489 added
Updated by Justin Sherrill almost 8 years ago
- Has duplicate Bug #19690: publish/promote content view does not update puppet environment repo's puppet install path added
Actions