Bug 1683786 - Satellite WebUI -> Monitor -> Dashboard shows incorrect information for 'Unregistered' status in 'Host Subscription Status' widget.
Summary: Satellite WebUI -> Monitor -> Dashboard shows incorrect information for 'Unre...
Keywords:
Status: CLOSED DUPLICATE of bug 1643432
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-27 19:07 UTC by Jayant Bhatia
Modified: 2019-08-12 19:32 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 19:43:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jayant Bhatia 2019-02-27 19:07:29 UTC
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.

Comment 3 Brad Buckingham 2019-03-01 19:43:22 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.