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:
Sync status page's content are not being displayed properly when we navigate from 
Puppet Environments page to Sync status page.

Version-Release number of selected component (if applicable):
- Satellite 6.7.0 snap 9

How reproducible:
- most of the time

Steps to Reproduce:
1. Go to Configure > Environments page.
2. from Puppet Environments page navigate to Sync status page (Content > Sync Status)

Actual results:
- Content of Page are not displayed properly.

Expected results:
- Content of Page are displayed properly.

Additional info:
- If unable to reproduce then logout from Satellite, close the browser and follow
above mentioned steps.

Created attachment 1654971 [details]
sync_status_page_issue

Verified with Satellite 6.8 SNAP2.1

Tested multiple times using steps from initial comment on Firefox and Chromium

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