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:

Satellite WebUI -> Monitor -> Dashboard, 'Host Subscription Status' widget provides links to lists of content hosts with [Invalid|partial|valid|unknown|unregistered] Subscriptions. It is showing invalid count on dashboard for 'Unregistered' status in 'Host Subscription Status' widget. However after clicking the figures in 'Unregistered' status it redirect to content host page where count is different.


Expected results: Count should be same on dashboard widget as equal to count in content host page.

Hi Jayant,

I am not seeing this behavior on early builds of Satellite 6.5.  When on the dashboard, clicking on 'Unregistered' (and the other options) takes the user to Content Hosts and displays the same number of hosts as is on the dashboard.   It appears this may have been solved by bug 1643432.

I am going to close this one as a duplicate; however, if the issue is observed after upgrading to 6.5 (coming later this year), please feel free to re-open.

Thanks!

*** This bug has been marked as a duplicate of bug 1643432 ***