Description of problem: Link in graph on capsule -> Puppet page have "undefined" as smart proxy name Version-Release number of selected component (if applicable): satellite-6.2.0-12.0.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Have Sat and Capsule with some hosts registered against Capsule 2. Go to Infrastucture -> Capsules -> <capsule> -> Puppet -> General -> Host Configuration Chart 3. Click on some segment of that pie/round graph Actual results: You are taken to https://<fqdn>/smart_proxies/undefined which does not exist Expected results: There should be no link or there should be a valid one
Created redmine issue http://projects.theforeman.org/issues/15287 from this bug
Upstream bug component is Capsule
Upstream bug assigned to tbrisker
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15287 has been resolved.
*** Bug 1411098 has been marked as a duplicate of this bug. ***
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. URL https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/hosts?search=last_report+%3E+%2235+minutes+ago%22+and+status.enabled+%3D+true+and+status.applied+%3D+0+and+status.failed+%3D+0+and+status.pending+%3D+0+and+puppet_proxy_id+%3D+%221%22 ---- https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/hosts?search=last_report+%3C+%2235+minutes+ago%22+and+status.enabled+%3D+true+and+puppet_proxy_id+%3D+%224%22 Search 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"
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. https://access.redhat.com/errata/RHSA-2018:0336