Bug #28877
closedPuppet classes are missing after adding a puppet module and content view publishing
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.
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/558 added
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy|509ca1cf7ac0958ff5021067c706b4474ada4de3.