Bug 1771507

Summary:	After 6.6 to 6.7 upgrade sync status detail page get broken with message like "Couldn't find Katello::Repository without an ID"
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Sync Plans	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Stephen Wadeley <swadeley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	egolov, jyejare, sajha
Target Milestone:	6.7.0	Keywords:	Regression, Triaged, Upgrades
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.14.0-0.4.rc2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:27:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Devendra Singh 2019-11-12 13:59:10 UTC

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:

Comment 8 Samir Jha 2019-11-18 18:23:30 UTC

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

Comment 10 Bryan Kearney 2019-11-19 19:01:46 UTC

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

Comment 14 errata-xmlrpc 2020-04-14 13:27:10 UTC

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