Red Hat Bugzilla – Bug 1167417
Content View Versions page takes a long time to list
Last modified: 2017-02-23 15:46:49 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/8491 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|1ced1c519b6dee549634d81536a6558b66dd88f7.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: RHEL66 / RHEL7 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-release-1.8.0-0.develop.201412111740git287d974.el6.noarch foreman-1.8.0-0.develop.201412111740git287d974.el6.noarch foreman-ovirt-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch foreman-postgresql-1.8.0-0.develop.201412111740git287d974.el6.noarch qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch foreman-compute-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el6.noarch foreman-vmware-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman-tasks-0.6.10-2.el6.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch foreman-selinux-1.8.0-0.develop.201411281557gitf4a857f.el6.noarch foreman-proxy-1.8.0-0.develop.201412111700gita7c8c34.el6.noarch qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.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-gce-1.8.0-0.develop.201412111740git287d974.el6.noarch foreman-libvirt-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman_bootdisk-4.0.2-1.el6.noarch rubygem-hammer_cli_foreman-0.1.4-1.201412111235git2131f5d.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