Project

General

Profile

Bug #18436

Puppet 4 upgrade does not change pulp's puppet_content_dir setting

Added by Daniel Kimsey over 5 years ago. Updated almost 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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.


Related issues

Is duplicate of Katello - Bug #17617: Content view publishing puppet modules to wrong directoryClosed2016-12-09

History

#1 Updated by Dominic Cleal over 5 years ago

  • Project changed from Foreman to Katello

#2 Updated by Daniel Kimsey over 5 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

#3 Updated by Daniel Kimsey over 5 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

#4 Updated by Justin Sherrill over 5 years ago

  • Status changed from New to Duplicate
  • Legacy Backlogs Release (now unused) set to 166

#5 Updated by Justin Sherrill over 5 years ago

  • Is duplicate of Bug #17617: Content view publishing puppet modules to wrong directory added

Also available in: Atom PDF