Bug 1631219

Summary: Dashboard - Host Configuration Status for all - Hosts with no reports - has a wrong query string
Product: Red Hat Satellite Reporter: Djebran Lezzoum <dlezzoum>
Component: DashboardAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Radovan Drazny <rdrazny>
Severity: low Docs Contact:
Priority: low    
Version: 6.4CC: dchaudha, dgupte, lzap, mhulan, mmccune, mpusater, rbertolj, smutkule
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/25005
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-01 13:31:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Dashboard from sat 6.3
none
sat - 6.3 Screenshot following hosts with no reports link none

Description Djebran Lezzoum 2018-09-20 08:55:43 UTC
Created attachment 1485058 [details]
Screenshot dashboard hosts with no reports

Description of problem:
Dashboard Host Configuration Status for all may show a number of "hosts with no reports" > 0, but when you follow the link from that component it redirect to hosts page that contain no hosts. 

Version-Release number of selected component (if applicable):
* candlepin-2.4.6-1.el7.noarch
* candlepin-selinux-2.4.6-1.el7.noarch
* foreman-1.18.0.26-1.el7sat.noarch
* foreman-bootloaders-redhat-201801241201-3.el7sat.noarch
* foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
* foreman-cli-1.18.0.26-1.el7sat.noarch
* foreman-compute-1.18.0.26-1.el7sat.noarch
* foreman-debug-1.18.0.26-1.el7sat.noarch
* foreman-discovery-image-3.5.2-1.el7sat.noarch
* foreman-ec2-1.18.0.26-1.el7sat.noarch
* foreman-gce-1.18.0.26-1.el7sat.noarch
* foreman-installer-1.18.0-1.el7sat.noarch
* foreman-installer-katello-3.7.0.4-1.el7sat.noarch
* foreman-libvirt-1.18.0.26-1.el7sat.noarch
* foreman-openstack-1.18.0.26-1.el7sat.noarch
* foreman-ovirt-1.18.0.26-1.el7sat.noarch
* foreman-postgresql-1.18.0.26-1.el7sat.noarch
* foreman-proxy-1.18.0.1-1.el7sat.noarch
* foreman-proxy-content-3.7.0-7.el7sat.noarch
* foreman-rackspace-1.18.0.26-1.el7sat.noarch
* foreman-selinux-1.18.0.1-1.el7sat.noarch
* foreman-vmware-1.18.0.26-1.el7sat.noarch
* katello-3.7.0-7.el7sat.noarch
* katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-6.noarch
* katello-certs-tools-2.4.0-2.el7sat.noarch
* katello-client-bootstrap-1.6.0-1.el7sat.noarch
* katello-common-3.7.0-7.el7sat.noarch
* katello-debug-3.7.0-7.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.7.0.4-1.el7sat.noarch
* katello-selinux-3.0.3-2.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.7.0-7.el7sat.noarch
* openldap-2.4.44-15.el7_5.x86_64
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-3.1.4-2.el7sat.noarch
* pulp-katello-1.0.2-5.el7sat.noarch
* pulp-maintenance-2.16.4.1-1.el7sat.noarch
* pulp-ostree-plugins-1.3.0-1.el7sat.noarch
* pulp-puppet-plugins-2.16.4-3.el7sat.noarch
* pulp-puppet-tools-2.16.4-3.el7sat.noarch
* pulp-rpm-plugins-2.16.4.1-2.el7sat.noarch
* pulp-selinux-2.16.4.1-1.el7sat.noarch
* pulp-server-2.16.4.1-1.el7sat.noarch
* python-ldap-2.4.15-2.el7.x86_64
* tfm-rubygem-ldap_fluff-0.4.7-2.el7sat.noarch
* tfm-rubygem-net-ldap-0.15.0-2.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1.Create some hosts 
2.Goto Dashboard 
3.Look at "Host Configuration Status for all" component => "hosts with no reports", that should show a number > 0 of not reported hosts

4.Click on "hosts with no reports"


Actual results:
No hosts listed


Expected results:
The same number of hosts indicated in the dashboard "hosts with no reports"

Additional info:
1- The query associated with "hosts with no reports" should be wrong, now the query is as following
'last_report > "30 minutes ago" and not has last_report and status.enabled = true'
as we can read this query should always lead to empty hosts list
see Screenshot hosts-with-no-reports-follow-link-from-dashboard.png

2- The link should be like it was in the past: 
'not has last_report and status.enabled = true'
see Screenshot hosts-with-no-reports-how-it-should-be.png

Comment 1 Djebran Lezzoum 2018-09-20 08:56:56 UTC
Created attachment 1485060 [details]
Screenshot hosts with no reports follow link from dashboard

Comment 2 Djebran Lezzoum 2018-09-20 08:57:54 UTC
Created attachment 1485063 [details]
Screenshot hosts with no reports how it should be

Comment 4 Lukas Zapletal 2018-09-21 10:02:20 UTC
Hello, I don't believe this is a regression, if you are able to attach screenshots from 6.3 I will happily put the flag back. Anyway:

TRIAGE: Low impact, easy workaround by editing URL or search. No backport.

Comment 5 Djebran Lezzoum 2018-09-21 10:11:22 UTC
Hi Lukas!
 
The automation test for 6.3 https://github.com/SatelliteQE/robottelo/blob/6.3.z/tests/foreman/ui/test_dashboard.py#L295
is passing without problem, any way will search a 6.3 box and put a screenshot from 6.3 here.

Comment 6 Djebran Lezzoum 2018-09-21 10:32:59 UTC
Created attachment 1485466 [details]
Dashboard from sat 6.3

Comment 7 Djebran Lezzoum 2018-09-21 10:34:05 UTC
Created attachment 1485467 [details]
sat - 6.3 Screenshot following hosts with no reports link

Comment 8 Djebran Lezzoum 2018-09-21 10:37:48 UTC
HI Lukas!

screenshot submitted the automation for 6.3 for the same test is passing and failing for 6.4.

I understand that that this is not a critical bug, but a regression for sure.
are we going to return the 6.4 flag and Regression keyword?

Comment 9 Satellite Program 2018-09-21 12:03:08 UTC
Upstream bug assigned to lzap

Comment 10 Satellite Program 2018-09-21 12:03:12 UTC
Upstream bug assigned to lzap

Comment 11 Lukas Zapletal 2018-09-21 12:22:36 UTC
Ok thanks, letting on the triage team to decide. Patch is pending review upstream.

Comment 15 Marek Hulan 2019-02-19 09:57:07 UTC
*** Bug 1651328 has been marked as a duplicate of this bug. ***

Comment 18 Pavel Moravec 2019-04-08 07:56:26 UTC
*** Bug 1691500 has been marked as a duplicate of this bug. ***

Comment 20 Bryan Kearney 2020-05-01 13:31:20 UTC
Satellite 6.4 is now End of Life. These bus will not be fixed on the 6.4 stream. Users of Satellite should upgrade to the latest version of Satellite to get access to the most current set of bugfixes and feature improvements.