Project

General

Profile

Bug #15821

When a Repository is removed from the Satellite Server, packages are still available in the Capsule Server

Added by Brad Buckingham almost 6 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Foreman Proxy Content
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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:
  1. foreman-rake katello:delete_orphaned_content RAILS_ENV=production >/dev/null
3. Execute Capsule sync from the Satellite Server
  1. hammer capsule content synchronize --id <ID>
4. Clear the yum cache over the Content host registered through the Capsule Server:
  1. rm -rf /var/cache/yum/*
  2. yum clean all
Actual results:
  1. yum repolist >>> It still list the disabled repository
Expected results:
  1. yum repolist >>> It should not list the disabled repository

Related issues

Blocks Katello - Tracker #15825: Sprint 1 : Content-FocusedNew2016-07-24

History

#1 Updated by Brad Buckingham almost 6 years ago

#2 Updated by Justin Sherrill almost 6 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
  • Legacy Backlogs Release (now unused) set to 166

Also available in: Atom PDF