Red Hat Bugzilla – Bug 1125330
Monitor Overview Host Configuration graph refers to incorrect URL
Last modified: 2017-02-23 16:08:59 EST
Description of problem: Monitor -> Dashboard -> Click on the Graph in 'Host Configuration Status' and it takes you to an 'undefined' URL: https://satellite/undefined (NB. I'm on IE 11 here) This is the HTML: <div class="col-md-6"> <a href="#" onclick="expand_chart(this); return false;"><h4 class="ca pie-title" data-original-title="Expand the chart" rel="twipsy"></h4></a><div class="statistics-pie small" data-series="[{"label":"Active","data":0,"color":"#4572A7"},{"label":"Error","data":0,"color":"#AA4643"},{"label":"OK","data":1,"color":"#89A54E"},{"label":"Pending changes","data":0,"color":"#80699B"},{"label":"Out of sync","data":0,"color":"#3D96AE"},{"label":"No report","data":0,"color":"#DB843D"},{"label":"Notification ...","data":0,"color":"#92A8CD"}]" data-title="Host Configuration Status" data-url="/hosts?search=search_by_legend" id="overview"></div>
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Connecting redmine issue http://projects.theforeman.org/issues/6232 from this bug
Upstream bug assigned to tbrisker@redhat.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/6232 has been closed ------------- Tomer Brisker Applied in changeset commit:5c5dabb2fda6ac2cf827dc415663d1a631d7dfc2.
VERIFIED *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el6.noarch foreman-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-client-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-client-cert-1.0-1.noarch foreman-ovirt-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el6.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el6.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el6.noarch foreman-libvirt-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el6.noarch foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el6.noarch qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.noarch foreman-compute-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch foreman-gce-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-proxy-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-broker-1.0-1.noarch foreman-postgresql-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch foreman-vmware-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch foreman-release-1.8.0-0.develop.201411131901gitd5f92b3.el6.noarch ruby193-rubygem-foreman-tasks-0.6.10-1.el6.noarch
This bug is slated to be released with Satellite 6.1.
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-2015:1592