Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17632 has been resolved.
Setting as triaged as there's a fix already upstream and a merge request downstream.
Verified in Satellite 6.2.8 Snap 3. All the behavior expected from the linked bugs is in place. See below for individual verification details.
Verified in 6.2.8 by QE
In 6.2.8 Snap 3, clicking a section of the chart brings you to the hosts page with a custom search entered. Examples below. This correctly shows the hosts that you would expect to see when clicking on said chart portion.
last_report > "35 minutes ago" and status.enabled = true and status.applied = 0 and status.failed = 0 and status.pending = 0 and puppet_proxy_id = "1"
last_report < "35 minutes ago" and status.enabled = true and puppet_proxy_id = "4"
In 6.2.8 Snap 3 I created a custom role with the filters seen in the attached images, then assigned that role to a new user. I then logged into that user and entered the search string "blah". There were no errors seen and the dashboard loaded correctly (verification screenshot 1). I then searched by a specific host collection and the results were filtered as expected (verification screenshot 2).
In 6.2.8 Snap 3 I reused the user and roles created for the bug above. I was then able to filter the dashboard by a specific compute resource, without errors (verification screenshot 3).
Created attachment 1256981 [details]
role filters 1
Created attachment 1256982 [details]
role filters 2
Created attachment 1256983 [details]
verification screenshot 1
Created attachment 1256984 [details]
verification screenshot 2
Created attachment 1256985 [details]
verification screenshot 3
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.