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:
Currently the correct_repositories rake script can handle re-creating and correcting repos that have missing bits.

Unfortunately for some scenarios, like BZ 1271300 - it is unable to take any action, due to the issue not allowing the repository to be created in pulp.

Version-Release number of selected component (if applicable): 6.2 and all prior.


How reproducible: 100% with environments run during repository renaming @ CDN.


Steps to Reproduce:
1. Utilize reproducer.

Actual results:
katello:correct_repositories tracebacks.

Expected results:
correct_repositories should do the following when it cannot properly create repos:
1. Needs to handle situations where it cannot correct repos due to being unable to create the pulp repository.
2. In that scenario, should also destroy katello instances of repo, and disable repository.
3. This should all be cleanly noted somewhere for review, so we understand what is happening and why.

Additional info:

Created attachment 1438228 [details]
Replacement 6.2.14 patch

Test on that patch is good with a local reproducer.

Actions it takes:

1. Checks for broken repos as it did before.
2. Tries to recreate repo in pulp if not there.
3. If create fails, instead delete all clones of repo from pulp/katello (in case of CV publish/promote with a half-existing repo) and then delete repo itself and disable the repo within Satellite.

Leaving open to propose for 6.2.16 if that time comes.

Moved to post since patch is attached, no upstream change.

Satellite 6.2 has reached maintenance support phase 2 [1]. Since this bug has a workaround in the form of a hotfix, it does not quality for inclusion in a 6.2.z release during this support phase. I am therefore closing this bug out.


[1] https://access.redhat.com/support/policy/updates/satellite