Bug #17620
closed
Content View Puppet repo not deleted from puppet master
Added by Brad Buckingham about 8 years ago.
Updated over 5 years ago.
Description
Description of problem:
When a Content View is removed from a lifecycle environment the published puppet repo is not deleted from the puppet master (/etc/puppet/environments directory)
Steps to Reproduce:
1. Create Content View
2. Add Puppet module
3. Publish Content View
4. Remove Content View From Environment Library
5. List the /etc/puppet/environments directory on the puppet master(s)
Actual results:
/etc/puppet/environments still contains a directory for the Content View
Expected results:
Directory of the Content View is deleted from /etc/puppet/environments
Additional notes:
It appears the pulp install distributor is not cleaning up after itself.
Fixing this issue will require modifications to both pulp and katello.
- Subject changed from Content View Puppet repo not deleted from puppet master
to Content View Puppet repo not deleted from puppet master
The associate Pulp feature adds an option which will allow you to have Pulp handle the directory cleanup on deletion. Once that issue is done Katello will need to use that option when creating the puppet_install_distributors.
https://pulp.plan.io/issues/2108
- Translation missing: en.field_release set to 211
- Difficulty set to easy
Required work for this bug:
- Updating the puppet_install_distributor to use the new option as detailed in https://pulp.plan.io/issues/2108 for existing repos on upgrade
- Removal of the cron job from katello-packaging which deletes these directories today
- Translation missing: en.field_release changed from 211 to 114
- Target version changed from Katello Backlog to Katello Recycle Bin
- Is duplicate of Bug #25576: Pulp should handle cleanup of Puppet directories added
- Status changed from New to Duplicate
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by