Bug 1651129

Summary: organization changed from Default org to [object Object] on sync status page in satellite WebUI.
Product: Red Hat Satellite Reporter: Jameer Pathan <jpathan>
Component: Sync PlansAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: high Docs Contact:
Priority: high    
Version: 6.5.0CC: ehelms, mhulan, walden
Target Milestone: 6.5.0Keywords: Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:38:54 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:
Attachments:
Description Flags
screenshot none

Description Jameer Pathan 2018-11-19 09:25:43 UTC
Description of problem:
organization changed from Default org to [object Object] on sync status page in satellite WebUI.

Version-Release number of selected component (if applicable):
@satellite 6.5.0 snap 4

How reproducible:
always

Steps to Reproduce:
1. go to Content > Sync Status page

Actual results:
- organization changed from Default organization to [object Object]

Expected results:
- organization should not change

Additional info:

Comment 1 Jameer Pathan 2018-11-19 09:29:12 UTC
Created attachment 1507150 [details]
screenshot

Comment 4 Marek Hulan 2018-11-30 14:47:33 UTC
The only page where this happens is in fact Sync Status. Even all new katello pages work. Could someone from sync page or someone more familiar with bastion take a look please? Moving to a different component.

Comment 6 Walden Raines 2018-12-05 16:17:07 UTC
Created redmine issue https://projects.theforeman.org/issues/25632 from this bug

Comment 7 John Mitsch 2018-12-06 15:56:00 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25228 from this bug

Comment 8 Satellite Program 2018-12-10 19:05:35 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25228 has been resolved.

Comment 9 Jameer Pathan 2018-12-27 06:08:53 UTC
Verified

@satellite 6.5.0 snap 9

steps:
1. go to Content > Sync Status page

Comment 12 errata-xmlrpc 2019-05-14 12:38:54 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-2019:1222