Bug 1231363

Summary:	If a package is removed from an upstream yum repo, a sync doesn't remove it from the Satellite repo
Product:	Red Hat Satellite	Reporter:	Frank Hirtz <fhirtz>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.8	CC:	bbuckingham, bkearney, riehecky
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-07 16:16:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Frank Hirtz 2015-06-12 19:55:34 UTC

Description of problem:
imagine a repository in an original state containing following packages:

A-1
A-2
B-1

Now upstream removes package A-2 and regenerates the metadata. One would expect that the published repo will contain:

A-1
B-1

after resync/republish. But satellite publishes again:

A-1
A-2
B-1

So in the end package A-2 is being installed for yum install A even though it's already gone from the repository. It is very misleading and this definitely shouldn't be a default behaviour or at least it should be clearly configurable.

Version-Release number of selected component (if applicable):
Satellite 6.1 beta/6.0.8

How reproducible:

Add new yum repo to the Satellite, sync it, remove package from the upstream yum repo and regenerate it's metadata, sync repo on Satellite.

Steps to Reproduce:
1. Add new yum repo to the Satellite and sync it
2. Remove package from the upstream yum repo and regenerate it's metadata
3. Re-sync the repo on the Satellite

Actual results:

The upstream removed package is still present in the Satellite repo

Expected results:

The upstream removed pacakage should be removed from the Satellite repo (by default or as a configurable behavior).
Additional info:

Comment 1 RHEL Program Management 2015-06-12 20:02:47 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2016-04-07 16:16:26 UTC

In Satellite 6.2, a feature, referred to as 'mirror on sync', is being introduced.  That feature should address the behavior requested by this BZ; therefore, going to close this one as a duplicate.  Thanks!

*** This bug has been marked as a duplicate of bug 1215672 ***