Bug #17617
closed
Content view publishing puppet modules to wrong directory
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 Leah Fisher over 7 years ago
I checked that the directory in the smart_proxy table was the /etc/puppetlabs/code/environments directory, but that doesn't seem to be what the publish is listening too. I also verified the pulp.yml foreman-proxy directory had the correct directory listed.
Updated by Justin Sherrill over 7 years ago
- Category set to 89
- Assignee set to Justin Sherrill
Updated by Justin Sherrill over 7 years ago
Looks like refreshing the smart proxy features should pull that value into the db again if it had changed. But even updating the db didn't seem to fully fix the problem so I'm going to look at this a bit more.
Updated by Justin Sherrill about 7 years ago
- Has duplicate Bug #18436: Puppet 4 upgrade does not change pulp's puppet_content_dir setting added
Updated by Daniel Kimsey about 7 years ago
Just noting the work-around discussed in IRC.
On Katello 3.2 installation on all katello & capsule instances:
sudo mv /etc/puppetlabs/code/environments /etc/puppetlabs/code/environments.theforeman.org#17617 sudo ln -s /etc/puppet/environments /etc/puppetlabs/code/
Updated by Daniel Kimsey about 7 years ago
After the above fix I had to re-version & publish content views to get the classes to show up in the puppet environments. Otherwise I'd see "class not in environment" on tooltips when trying to add the class to the host(groups?).
Updated by Eric Helms about 7 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 7 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 7 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 7 years ago
- Pull request https://github.com/Katello/katello/pull/6651 added
Updated by Eric Helms about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|2b86ed7e8d19977dc47a6d10159b88146213441f.
Updated by The Foreman Bot about 7 years ago
- Pull request https://github.com/Katello/katello-installer/pull/489 added
Updated by Justin Sherrill almost 7 years ago
- Has duplicate Bug #19690: publish/promote content view does not update puppet environment repo's puppet install path added