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: Unable to switch organization for "sync status" page when user is in Any Context.


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


How reproducible: Always


Steps to Reproduce:
1. Set "Any Organization" and "Any Location" on top
2. Click on Content -> "Sync Status"
3. "Select an Organization" page will come up. 
4. Select organization in dropdown and press Select

Actual results:  It Stay on "Select an Organization" page


Expected results: After press on Select. It should go Sync Status page and correct organization should be listed on the top


Additional info:
[root@vm253-219 ~]# rpm -qa satellite
satellite-6.8.0-0.7.beta.el7sat.noarch
[root@vm253-219 ~]# rpm -qa foreman
foreman-2.1.0.1-1.el7sat.noarch
[root@vm253-219 ~]# rpm -qa katello
katello-3.16.0-0.4.rc4.el7sat.noarch

Upstream bug assigned to paji

Upstream bug assigned to paji

*** Bug 1866246 has been marked as a duplicate of this bug. ***

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30580 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 (Important: Satellite 6.8 release), 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:4366