Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Within Satellite 6, it is difficult to see (if at all possible) in a tabular format:
'available' errata - Errata that can directly be installed on the system. I.e. What will land on the server when 'yum update' is run.
'applicable' errata - Errata that applies to the system based upon the lineage of its content views, but may not be published/promoted yet.
Having the ability to see this information via the UI/API & CLI makes it very easy for the end user to do reporting for compliance, auditing and general change management reasons much simpler.
At a minimum, an equivalent to 'spacewalk-report errata-list' for BOTH 'available' and 'applicable' errata would satisfy this RFE.
#spacewalk-report --list-fields-info errata-list
advisory: Advisory / errata identifier
type: Advisory type (Enhancement, Bug Fix, Security)
cve: List of CVE names (Common Vulnerabilities and Exposures Identifiers) addressed by the errata
synopsis: Synopsis of the errata
systems_affected: Number of systems to which this errata is applicable
Comment 1RHEL Program Management
2014-08-04 20:13:54 UTC
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.
I would argue that Satellite 6 should be considered incomplete without an equivalent to the Satellite 5.x web GUI view showing "Systems - All" (and arguably, the Sat 5.x built-in views for "out-of-date", "virtual", "Unentitled", etc. should be included as well).
Removing this functionality is a big step backwards, and users at my institution will not be happy about it (makes it very difficult to monitor patch currency without writing custom reports (how??) or tediously clicking through the 'details' views for each system, one-by-one).
This is implemented in Satellite 6.1 as part of our Errata Management Feature. You can view applicable vs available and compare the current Content Host vs previous Lifecycle Environments to see where the errata is.
Comment 12sthirugn@redhat.com
2015-03-17 20:48:40 UTC
Verified in Satellite-6.1.0-RHEL-6-20150311.1
Now there is a new Content -> Errata page in which we have capabilities to filter errata with specific repo, filter with applicable/installable types and directly install from this page as incremental updates as well. Please reopen this bug or open new bugs if you feel anything is missing.
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-2015:1592