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.
Bug 1215672 - [RFE] option to clear repository prior to re-sync
Summary: [RFE] option to clear repository prior to re-sync
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1231363 1308895 (view as bug list)
Depends On:
Blocks: 260381 GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2015-04-27 12:49 UTC by Tom McKay
Modified: 2019-12-16 04:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-10 23:52:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13208 0 None None None 2016-04-22 15:01:24 UTC

Description Tom McKay 2015-04-27 12:49:43 UTC
During development of a product, each sync of a repository could bring in or remove packages. For example

upstream packages: a.1, b.1
sync and publish cv version 1: a.1, b.1

upstream packages: a.2, b.1
sync and publish cv version 2: a.1, a.2, b.1

upstream packages: a.3
sync and publish cv version 3: a.1, a.2, a.3, b.1

Note that on the third sync and publish, b.1 still will exist in the katello product. This means that if the removal of b.1 from the source upstream url, testing of the product against katello would still be able to resolve that dependency.

The RFE is to allow an option to remove all existing packages prior to sync. With this option enabled, cv version 3 would be: a.3

Comment 1 Tom McKay 2015-04-27 12:49:44 UTC
Created from redmine issue http://projects.theforeman.org/issues/10277

Comment 2 Bryan Kearney 2015-08-25 18:35:12 UTC
Upstream bug component is Content Views

Comment 3 Bryan Kearney 2016-01-27 21:04:31 UTC
Upstream bug assigned to paji

Comment 4 Bryan Kearney 2016-01-27 21:04:34 UTC
Upstream bug component is Content Management

Comment 5 Bryan Kearney 2016-02-23 19:09:03 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/13208 has been closed
-------------
Partha Aji
Applied in changeset commit:katello|7de1b3ef3befe35477c6fe2750db9e30e1de3a38.

Comment 7 Brad Buckingham 2016-04-07 16:16:26 UTC
*** Bug 1231363 has been marked as a duplicate of this bug. ***

Comment 8 Brad Buckingham 2016-04-19 19:53:15 UTC
*** Bug 1308895 has been marked as a duplicate of this bug. ***

Comment 9 Lukas Pramuk 2016-04-29 14:41:54 UTC
FailedQA.

@Sat6.2.0-Beta
pulp-server-2.8.1.3-1.el6sat.noarch

Not to mess up with a repo creation I simply used two different Beta Snaps to test it.

1. Created repo and synced Snap9.3 to it. (publish CV version 1)
2. Change repo URL to point to Snap6.1 a sync it (publish CV version 2)
3. Check repository content

I expected that packages that are only in snap9.3 and not in snap6.1 would be removed from the repository... but they are not

To doublecheck this scenario I also involved CV publishing and the result was that both CV versions contained the same number of packages.

Can you pls confirm that this above is a valid testing scenario for this RFE?

Comment 11 Partha Aji 2017-07-10 23:52:39 UTC
This was included with the "Mirror on Sync" policy in 6.2. Closing as CURRENTRELEASE. Please re-open if any issues are found


Note You need to log in before you can comment on or make changes to this bug.