Project

General

Profile

Actions

Bug #28877

closed

Puppet classes are missing after adding a puppet module and content view publishing

Added by Ewoud Kohl van Wijngaarden over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:
When adding a puppet module containing some classes and publishing related content view, those classes are not created or imported to the Satellite.

How reproducible:
always

Steps to Reproduce:
1. create new product
2. create new puppet repo and synchronize it
3. create new content view and add the module
4. publish the content view - new puppet environment is created
5. check UI -> Configure -> Classes or <fqdn>/api/v2/puppetclasses or 'hammer host puppet-classes'

Actual results:
classes from the module are missing

Expected results:
classes from the module should be present

Additional notes:
When passing in --foreman-proxy-plugin-pulp-puppet-content-dir /etc/puppetlabs/code/environments it does work. The actual value is a /tmp/tmp_ which means Kafo started setting the environmentpath to the temporary path.

Actions #1

Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/558 added
Actions #2

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases 2.0.0 added
Actions #3

Updated by Ewoud Kohl van Wijngaarden over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF