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:

post upgrading to satellite 6.2 all content hosts in the webui have black dots for subscriptions and have no information about them including "never checked in"

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


How reproducible: 50%


Steps to Reproduce:
1. upgrade to 6.2
2. go to content host page
3. 

Actual results:

will attach screen shots. this is causing confusion since even going to a client and manually updating katello-agent doesn't resolve.

Expected results: after upgrade content hosts are literally any color other than black.

Additional info: after we clear the cache of firefox ( sometimes ) or just switch to chrome this issue goes away.

clearing the cache resolve the issue. Confirmed 01683175

Ashfaqur:

Clearing which cache resolved the issue?

I cleared my browser cache to fix this issue

Also the content hosts state they are all "invalid" and black dots. Resolved with clearing cache of firefox/chrome

Bryan : yes, resolved after clearing the cache.

We have not seen a case since Novemeber, so I am closing this out. If you do see this again please feel free to re-open with additional information.