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: After 6.6 to 6.7 upgrade sync plan detail page get broken with the message like "Couldn't find Katello::Repository without an ID"


Version-Release number of selected component (if applicable):
6.7

How reproducible:
1/1

Steps to Reproduce:
1. Prepared the setup to perform upgrade from 6.6 to 6.7
2. Created all the required repository to perform the upgrade operation
3. Unlock the foreman-maintain packages installation to perform the yum update
4. Trigger yum update
5. yum update completed successfully
6. Executed satellite upgrade "satellite-installer --scenario satellite --upgrade"
7- Upgrade get completed successfully.
8- Login via UI and go to the sync status tab and expand the details to get a lot of unexpected messages.

Actual results:
Sync status details page get broken

Expected results:
Sync status details page should not be broken.

Additional info:

Created redmine issue http://projects.theforeman.org/issues/28291 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28291 has been resolved.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454