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:

For yum repos sometimes content on the filesystem becomes corrupt or missing.  Pulp provides the ability to do this but katello needs to support it.

katello would need to:

1) switch the repo to on_demand if its immediate (possibly just in pulp)
2) sync the repo
3) kick off a 'download' task with verify_all_units set to true
4) change the repo back to 'immediate' if needed 


more info:


https://docs.pulpproject.org/user-guide/deferred-download.html#re-using-files-on-disk-when-db-is-lost

Not entirely.  I think we need some design around this.  There are two different scenarios here:

a) You want to force pulp to sync the repository again, but pulp doesn't think it needs to so it just skips most of the steps.  Lets call this force sync.

b) There is some rpm corruption and you want pulp to verify all of the checksums locally on the filesytem and redownload anything that is corrupt.  Lets call this Repair and Sync


I know of three bzs that cover these situations I believe:

a) Force Sync
https://bugzilla.redhat.com/show_bug.cgi?id=1421250

b) Repair and Sync
https://bugzilla.redhat.com/show_bug.cgi?id=1421232
https://bugzilla.redhat.com/show_bug.cgi?id=1223023


And it is possible that we could combine both of these into one user action, however i imagine b) will take quite a bit longer, is quite a bit more complex, and likely won't be needed as much as a) (in my experience).  So I think This is a dupe of 1223023

I will close this BZ and retitle 1223023 accordingly.

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