Actions
Bug #15821
closedWhen a Repository is removed from the Satellite Server, packages are still available in the Capsule Server
Status:
Rejected
Priority:
Normal
Assignee:
Category:
Foreman Proxy Content
Target version:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1305002
Description of problem:
When a Repository is removed from the Satellite Server, packages are still available in the Capsule Server
Version-Release number of selected component (if applicable):
Satellite Server v.6.1.6
How reproducible:
Steps to Reproduce:
>>> Over the Satellite Server :
1. Disable a Repository from the Satellite Server
Log in to Satellite --> Content --> Red Hat Repository --> Unchecked the Repository that needs to be disabled
2. Clear the Orphan Packages over the Capsule Server:
- foreman-rake katello:delete_orphaned_content RAILS_ENV=production >/dev/null
3. Execute Capsule sync from the Satellite Server
- hammer capsule content synchronize --id <ID>
4. Clear the yum cache over the Content host registered through the Capsule Server:
- rm -rf /var/cache/yum/*
- yum clean all
Actual results:
- yum repolist >>> It still list the disabled repository
Expected results:
- yum repolist >>> It should not list the disabled repository
Updated by Brad Buckingham about 8 years ago
- Blocks Tracker #15825: Sprint 1 : Content-Focused added
Updated by Justin Sherrill about 8 years ago
- Subject changed from When a Repository is removed from the Satellite Server, packages are still available in the Capsule Server to When a Repository is removed from the Satellite Server, packages are still available in the Capsule Server
- Status changed from New to Rejected
- Translation missing: en.field_release set to 166
Actions