Bug #18436
closedPuppet 4 upgrade does not change pulp's puppet_content_dir setting
Description
I followed the Puppet 4 upgrade instructions for my Katello 3.2 and Capsule systems, but found myself unable to publish new classes to the KT_* environments.
I finally tracked it down to the fact that pulp is putting the sync'd content in the wrong place.
The puppetserver is configured to look in @/etc/puppetlabs/code/environments
@, but pulp is configured to publish content to @/etc/puppet/environments
@, the old Puppet 3 location.
Puppet client shows the following error from the puppetservers:
Error 500 on SERVER: {"message":"Server Error: Could not find a directory environment named 'KT_myorg_development_cv_os_rhel_el7_8' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?","issue_kind":"RUNTIME_ERROR","stacktrace":["Warning: The 'stacktrace' property is deprecated and will be removed in a future version of Puppet. For security reasons, stacktraces are not returned with Puppet HTTP Error responses."]}
Pulp configuration on the katello instance
$ ack /etc/puppet/ settings.d/pulp.yml 8::puppet_content_dir: /etc/puppet/environments settings.d/pulpnode.yml 8::puppet_content_dir: /etc/puppet/environments
Puppet server configuration (I think..)
$ puppet config print modulepath /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
Katello server package versions
$ puppet --version 4.8.1 $ rpm -q foreman foreman-1.13.3-1.el7.noarch
What I don't know, is how to effect a change so I can work-around this.
Updated by Dominic Cleal almost 8 years ago
- Project changed from Foreman to Katello
Updated by Daniel Kimsey almost 8 years ago
Clarification.
Pulp configuration for foreman-proxy on the katello instance:
$ ack "/etc/puppet/" /etc/foreman-proxy/
settings.d/pulp.yml
8::puppet_content_dir: /etc/puppet/environments
settings.d/pulpnode.yml
8::puppet_content_dir: /etc/puppet/environments
I believe these values need to be set to: /etc/puppetlabs/code/environments
Updated by Daniel Kimsey almost 8 years ago
Other hard-coded paths to the old locations:
[root@katello etc]# ack '/etc/puppet/environments' cron.weekly/katello-clean-empty-puppet-environments 7:[ -d /etc/puppet/environments ] && find /etc/puppet/environments/KT* -maxdepth 0 -type d -empty -delete foreman-proxy/settings.d/pulpnode.yml 9::puppet_content_dir: /etc/puppet/environments foreman-proxy/settings.d/pulp.yml 9::puppet_content_dir: /etc/puppet/environments puppet/puppet.conf.rpmsave 31: environmentpath = /etc/puppet/environments 32: basemodulepath = /etc/puppet/environments/common:/etc/puppet/modules:/usr/share/puppet/modules foreman-installer/scenarios.d/katello-answers.yaml 298: puppet_content_dir: /etc/puppet/environments
Updated by Justin Sherrill almost 8 years ago
- Status changed from New to Duplicate
- Translation missing: en.field_release set to 166
Updated by Justin Sherrill almost 8 years ago
- Is duplicate of Bug #17617: Content view publishing puppet modules to wrong directory added