Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1150674

Summary:	bulk errata 'affected content hosts' column is blank
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
WebUI sub component:	Katello	QA Contact:	sthirugn <sthirugn>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	achan, asogukpi, bbuckingham, cwelton, jmontleo, michele, nstrug, sthirugn
Version:	6.0.4	Keywords:	Triaged
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, when selecting a system with applicable errata and going to the bulk actions pane in the errata tab, the errata show up but the 'applicable content hosts' column is blank. It now shows a clickable number in the bulk actions pane that goes to the list of content hosts.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-13 22:29:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1122832

Description Justin Sherrill 2014-10-08 15:51:26 UTC

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.

Comment 2 Justin Sherrill 2014-10-14 14:20:26 UTC

https://gitlab.sat.lab.tlv.redhat.com/satellite6/katello/merge_requests/37

Comment 5 sthirugn@redhat.com 2014-11-04 15:49:49 UTC

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

Comment 6 sthirugn@redhat.com 2014-11-04 16:29:37 UTC

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

Comment 8 errata-xmlrpc 2014-11-13 22:29:41 UTC

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