Bug #17617: Content view publishing puppet modules to wrong directory - Katello - Foreman

Custom queries

All issues closed in the last 3 weeks
Assigned to me
Closed Issues without Release
Easy and Trivial Issues
Good first issues - Foreman core
Katello 4.15.1 TODO
Mine
My issues closed in the last 3 weeks
open docker issues 2.1
Open Features
Open Katello issues by target version
Open Pull Requests
Stale
Trackers
Untriaged
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #17617

closed

Content view publishing puppet modules to wrong directory

Added by Leah Fisher almost 8 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Eric Helms

Category:

Target version:

Katello 3.3.1

Difficulty:

Triaged:

Bugzilla link:

1420868

Pull request:

https://github.com/Katello/katello-installer/pull/486, https://github.com/Katello/katello/pull/6651, https://github.com/Katello/katello-installer/pull/489

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

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

Related issues 3 (0 open — 3 closed)

Has duplicate Katello - Bug #18436: Puppet 4 upgrade does not change pulp's puppet_content_dir setting	Duplicate		02/08/2017	Actions
Has duplicate Katello - Bug #18131: foreman-installer --upgrade-puppet fails to set new paths for foreman-installer	Duplicate		01/18/2017	Actions
Has duplicate Katello - Bug #19690: publish/promote content view does not update puppet environment repo's puppet install path	Duplicate	Justin Sherrill	05/26/2017	Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Leah Fisher almost 8 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.

Actions

Copy link

Updated by Justin Sherrill almost 8 years ago

Category set to 89
Assignee set to Justin Sherrill

Actions

Copy link

Updated by Justin Sherrill almost 8 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.

Actions

Copy link

Updated by Justin Sherrill almost 8 years ago

Has duplicate Bug #18436: Puppet 4 upgrade does not change pulp's puppet_content_dir setting added

Actions

Copy link

Updated by Justin Sherrill almost 8 years ago

Bugzilla link set to 1420868

Actions

Copy link

Updated by Daniel Kimsey almost 8 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/

Actions

Copy link

Updated by Daniel Kimsey almost 8 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?).

Actions

Copy link