Bug #17620
closed
Content View Puppet repo not deleted from puppet master
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.
Updated by Brian Bouterse about 8 years ago
- 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.
Updated by Justin Sherrill about 8 years ago
- Translation missing: en.field_release set to 211
- Difficulty set to easy
Updated by Justin Sherrill almost 8 years ago
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
Updated by Justin Sherrill almost 8 years ago
- Translation missing: en.field_release changed from 211 to 114
Updated by Jonathon Turel over 5 years ago
- Target version changed from Katello Backlog to Katello Recycle Bin
Updated by Jonathon Turel over 5 years ago
- Is duplicate of Bug #25576: Pulp should handle cleanup of Puppet directories added