Bug 1648473

Summary: In satellite 6.4 under the Content -> Packages -> Enter Package Name->Details Sections , the installed on,applicable to,upgradable for shows as 0 hosts.
Product: Red Hat Satellite Reporter: Vikas Wariyal <vwariyal>
Component: Errata ManagementAssignee: Michael Johnson <micjohns>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: heidelberg.david, inecas, zhunting
Target Milestone: 6.5.0Keywords: Regression, Triaged, Upgrades
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:38: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:
Attachments:
Description Flags
Issue
none
Correct Host none

Description Vikas Wariyal 2018-11-09 20:04:47 UTC
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:

Comment 1 Vikas Wariyal 2018-11-09 20:05:25 UTC
Created attachment 1503847 [details]
Correct Host

Comment 6 Michael Johnson 2019-01-07 15:22:39 UTC
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.

Comment 7 Brad Buckingham 2019-01-08 16:11:31 UTC
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.

Comment 8 Perry Gagne 2019-01-24 20:10:16 UTC
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

Comment 11 errata-xmlrpc 2019-05-14 12:38: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/RHSA-2019:1222