Description of problem: When selecting a system with applicable errata and going to the bulk actions pane, errata tab, the errata show up but the 'applicable content hosts' column is blank. It should show a number in the column that is clickable to go to the list of content hosts. Version-Release number of selected component (if applicable): Satellite 6.0.4 How reproducible: Always Steps to Reproduce: 1. Sync rhel 2. Register a content host with katello-agent installed (ensure the system is not fully up to date). 3. Go to Content Hosts 4. select the checkbox by the content host 5. click bulk actions 6. click the errata tab Actual results: Errata are shown, but applicable content hosts column is empty Expected results: It should show a number in the column that is clickable to go to the list of content hosts. Additional info: When clicking on the errata, most of the details are missing so it seems like a big chunk of each errata is not being sent down.
https://gitlab.sat.lab.tlv.redhat.com/satellite6/katello/merge_requests/37
Failed. Unable to consume content in registered host. See https://bugzilla.redhat.com/show_bug.cgi?id=1160351 Version Tested: Satellite-6.0.4-RHEL-6-20141029.5 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23.1-1.el6.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23.1-1.el6.noarch * candlepin-tomcat6-0.9.23.1-1.el6.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.47-1.el6sat.noarch * foreman-compute-1.6.0.47-1.el6sat.noarch * foreman-gce-1.6.0.47-1.el6sat.noarch * foreman-libvirt-1.6.0.47-1.el6sat.noarch * foreman-ovirt-1.6.0.47-1.el6sat.noarch * foreman-postgresql-1.6.0.47-1.el6sat.noarch * foreman-proxy-1.6.0.30-1.el6sat.noarch * foreman-selinux-1.6.0.15-1.el6sat.noarch * foreman-vmware-1.6.0.47-1.el6sat.noarch * katello-1.5.0-30.el6sat.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.64-1.el6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-8.el6.x86_64 * openldap-devel-2.4.39-8.el6.x86_64 * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.4.3-0.1.beta.el6sat.noarch * pulp-nodes-parent-2.4.3-0.1.beta.el6sat.noarch * pulp-puppet-plugins-2.4.3-1.el6sat.noarch * pulp-puppet-tools-2.4.3-1.el6sat.noarch * pulp-rpm-plugins-2.4.3-1.el6sat.noarch * pulp-selinux-2.4.3-1.el6sat.noarch * pulp-server-2.4.3-1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
Verified. 1. Now the Affected Content hosts is populated with a number - clicking which it shows the affected hosts. Clicking on "Back to Errata List" takes me back to the Errata list 2. I had two content hosts and applied an errata x on one of the hosts. Retesting this bug correctly showed 1 Affected Content Hosts for errata x Version Tested: Satellite-6.0.4-RHEL-6-20141029.5 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23.1-1.el6.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23.1-1.el6.noarch * candlepin-tomcat6-0.9.23.1-1.el6.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.47-1.el6sat.noarch * foreman-compute-1.6.0.47-1.el6sat.noarch * foreman-gce-1.6.0.47-1.el6sat.noarch * foreman-libvirt-1.6.0.47-1.el6sat.noarch * foreman-ovirt-1.6.0.47-1.el6sat.noarch * foreman-postgresql-1.6.0.47-1.el6sat.noarch * foreman-proxy-1.6.0.30-1.el6sat.noarch * foreman-selinux-1.6.0.15-1.el6sat.noarch * foreman-vmware-1.6.0.47-1.el6sat.noarch * katello-1.5.0-30.el6sat.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.64-1.el6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-8.el6.x86_64 * openldap-devel-2.4.39-8.el6.x86_64 * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.4.3-0.1.beta.el6sat.noarch * pulp-nodes-parent-2.4.3-0.1.beta.el6sat.noarch * pulp-puppet-plugins-2.4.3-1.el6sat.noarch * pulp-puppet-tools-2.4.3-1.el6sat.noarch * pulp-rpm-plugins-2.4.3-1.el6sat.noarch * pulp-selinux-2.4.3-1.el6sat.noarch * pulp-server-2.4.3-1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
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/RHBA-2014:1857