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 1477205 [details]
Reference Screenshots

Description of problem:

Satellite 6.3 , 'Content Host Counts' is showing incorrect for Applicable and Upgradable under Package

Version-Release number of selected component (if applicable):

Satellite 6.3.2

How reproducible:

Always

Steps to Reproduce:

1. on Web GUI : Content => Packages => Check 'Applicable and Upgradable' content host count for any package.

2. Now click on same package and see "Applicable To" and "Upgradable For" Host count, and this count would be just opposite then you saw before click on package.

3. Attached screen shots for more reference.

Actual results:

Content host Count always shows incorrect for "Applicable To" and "Upgradable For".

Expected results:

Content host count should be correct for "Applicable To" and "Upgradable For".

Additional info:

Thanks for the bugzilla.  The behavior described appears to be a duplicate of bug 1588880.

*** This bug has been marked as a duplicate of bug 1588880 ***