Bug 1187338

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

So this bz covers two aspects:

1) your applicable errata list is empty (this seems as though something is misconfigured), please contact support or someone on irc to resolve this.  

It could be:
* that katello-agent is not installed on the client
* the wrong version is installed
* goferd is not running on the client
* the system is not subscribed to the correct product
* the system has an incorrect release version set

Any of those issues could cause this behavior.

2) An RFE for package applicability management on the scale of sat5.  This is a large feature and likely cannot make 6.1

I propose we move this to sat 6.2

(In reply to Justin Sherrill from comment #4)
> So this bz covers two aspects:
> 
> 1) your applicable errata list is empty (this seems as though something is
> misconfigured), please contact support or someone on irc to resolve this.  
> 
> It could be:
> * that katello-agent is not installed on the client
> * the wrong version is installed
> * goferd is not running on the client
> * the system is not subscribed to the correct product
> * the system has an incorrect release version set
> 
> Any of those issues could cause this behavior.
> 
> 2) An RFE for package applicability management on the scale of sat5.  This
> is a large feature and likely cannot make 6.1
> 
> I propose we move this to sat 6.2

Just to let you know:
we have a RHEL6.4 client host which has katello-agent-1.5.3-7.el6sat.noarch installed. 
goferd is running. 
The system show us on satellite under "Content Hosts" => Host Details as Installed Product "Red Hat Enterprise Linux Server 6.6" (Which should be RHEL6.4 because we run the 2.6.32-358.18.1.el6.x86_64 kernel).
On satellite we have set the Release Version of the hosts to "6Server",
because we want to get all updates but exclude only kernel* and redhat-release* in the given Content View.

FYI

Hi Justin,

Is point 2) from comment 4 addressed by your upstream changes to support package applicability?  

If so, should we move this to ON_QA for 6.3?

Regarding point 1), it is unclear if there was any progress on it; however, the case has since been closed and we have no other reports that I am aware of from other users.

Brad,

Based on the original description, yes I would say this is resolved upstream and thus will make 6.3.  I would move to on_qa for 6.3

Thanks Justin!

As there is no upstream tracker assigned and no comment regarding exact expected functionality present, I am treating this BZ as "Sat6 should be able to show upgradable packages of a host and remotely upgrade the chosen packages" as it seems most related to the OP.

Verified with Sat6.3, snap 17.

Compared to Sat5, I actually miss some functionality; examples I can think of now:
1) Install the latest package version. You have to choose exact version. Workaround: check all versions and the newesst one will be installed. Related: The number of updates shown includes all possible versions of the package higher than the installed one.
2) Determine which repo the upgrades come from.
3) Other patch management functionality not related to upgrading, like ability to choose a package to be installed from a list.

However, the basic package upgrade management functionality, i.e. listing upgrades and remote upgrading, works. See Content Hosts -> <content_host> -> Packages -> Applicable.

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-2018:0336