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.

Created attachment 1503846 [details]
Issue

Description of problem:

In satellite 6.4 under the Content -> Packages -> Enter Package Name -> Details Sections , the installed on, applicable to, upgradable for shows as 0 hosts while clicking on 0 hosts shows the correct host on which the package is installed.

Version-Release number of selected component (if applicable):
satellite-6.4.0-15.el7sat.noarch


How reproducible:
Seen both in upgrade from Satellite 6.3 and fresh installation

Steps to Reproduce:
1.In Satellite GUI -> Content -> Packages -> Enter Package Name(katello-agent) -> Details Sections 
2. Shows 0 Hosts for the searched package in all 3 parameters.
3. After Clicking on the O Hosts shows the correct host on which the package installed.

Actual results:
0 Hosts

Expected results:
The no of host on which the package is installed.

Additional info:

Created attachment 1503847 [details]
Correct Host

This bug was fixed in 6.5. Here's the commit for the fix: 660e9794af46b3f614b54fe0f2c9375a169f3613

https://github.com/theforeman/foreman/pull/6254

Let me know of any additional details you need.

Note: the referenced code changes have already been included in the 6.5 build and verified as part of bug 1642549.  Associating the redmine; however, nothing additional should need to be pulled in.

Verified fix in 6.5 snap 12. 

Installed 2 different versions of vim-enhanced on 2 hosts and verify that the package details showed the correct info about which hosts it was installed/applicable/upgradable to

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-2019:1222