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.
Bug 1651328 - Host reported on the satellite's dashboard shows empty results when clicked on the link.
Summary: Host reported on the satellite's dashboard shows empty results when clicked o...
Keywords:
Status: CLOSED DUPLICATE of bug 1631219
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dashboard
Version: 6.4.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Sebastian Gräßl
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-19 17:28 UTC by sandeep mutkule
Modified: 2023-10-06 18:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-19 09:57:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1631219 0 low CLOSED Dashboard - Host Configuration Status for all - Hosts with no reports - has a wrong query string 2023-10-06 17:55:33 UTC

Internal Links: 1631219

Description sandeep mutkule 2018-11-19 17:28:10 UTC
Description of problem:
Host reported on the satellite's dashboard under "Host Configuration" section gives an empty output when clicked on the link of the number of hosts reported.


Version-Release number of selected component (if applicable):
Red Hat Satellite 6.4.0


Steps to Reproduce:
1. Register/provision the client systems from the satellite server and do not power them on,
   Until puppet has been installed they should show up in the Overview page as "Hosts with no reports.
   
2. Now navigate to Monitor -> Dashboard. You will see the amount of newly created servers under the Host configuration status,
    However, when you click on the Host configuration or on the Hosts with alerts disable status link, the search turns up empty.



Actual results:
Number hosts reported on the satellite's dashboard shows empty results when clicked on the link.


Expected results: 
Clicking on the link should show the servers that are in the "no reports" or "alerts disabled" status.


Additional info:
when customer modifies the search a little bit, the "hosts with no reports" do show up, as do the "hosts with alerts disabled".

Comment 1 Marek Hulan 2018-11-20 08:00:06 UTC
Might be similar to BZ #1631219, Sebastian, mind to take a look?

Comment 2 Sebastian Gräßl 2018-11-21 06:56:38 UTC
Can you elaborate more, Sandeep. 

There are now 3 "Host Configuration" widgets, for Ansible, Puppet and one for hosts that have no association with both. 

When a host is created and has no reports yet it will appear in the "Host Configuration Status for All". Once reports have been coming in for these hosts they will appear under "Host Configuration Status for Puppet".

Comment 8 Marek Hulan 2019-02-19 09:57:07 UTC
I believe this is a duplicate of BZ 1631219, I looked at the first attached case and it seems the cause is we're adding the time stamp. See BZ 1631219 for more details. Please reopen, if I missed something.

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


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