Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 1RHEL 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.
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 ***