Description of problem:
As a user of Satellite 6.1, I would like the ability to see on the 'Content Hosts' page (Hosts->Content-Hosts) of the Satellite the number of packages (RPMs) that a host needs to become fully updated.
Version-Release number of selected component (if applicable):
Today on the content-hosts page, we list installable errata (RHEA|RHBA|RHSA). However, much of my content is synchronized in from yum repositories that do not provide errata metadata. Thus, my content views are created from a mix of sources; some with errata metadata; some without.
Having this capability prominently displayed will allow me to determine how many packages need to be updated on a content-host.
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.
Upstream bug component is WebUI
Per 6.3 planning, moving out non acked bugs to the backlog
*** Bug 1239329 has been marked as a duplicate of this bug. ***
Upstream bug assigned to jsherril
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/5148 has been resolved.
Verified with Satellite 6.3 SNAP 14: satellite-6.3.0-17.0.beta.el7sat.noarch, tfm-rubygem-katello-3.4.5-1.el7sat.noarch
With Satellite 6.3, user can now see a summary from the Content Hosts listing on the number packages that need upgrading on the content host. In addition, they can go to the content host (Packages -> Applicable Packages) to see the list and perform package upgrades.
Attaching screenshots of the new UI.
Created attachment 1322798 [details]
Satellite 6.3 - Content Host listing - shows package updates needed
Created attachment 1322799 [details]
Satellite 6.3 - Content Host - Applicable Packages
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.