Bug 1394360 - Handle errata status with Library vs current environment
Summary: Handle errata status with Library vs current environment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.2.0
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Brad Buckingham
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1368254
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 19:52 UTC by Bryan Kearney
Modified: 2020-07-16 09:00 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368254
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12347 0 High Closed Handle errata status with Library vs current environment 2020-05-28 14:18:00 UTC
Red Hat Knowledge Base (Solution) 2678781 0 None None None 2016-11-11 19:52:17 UTC

Comment 2 Bryan Kearney 2016-11-11 21:21:34 UTC 
Upstream bug assigned to jsherril
Comment 3 Bryan Kearney 2016-11-11 21:21:39 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/12347 has been resolved.
Comment 4 Brad Buckingham 2017-08-30 20:30:38 UTC 
Verified with Satellite 6.3 SNAP 13 : satellite-6.3.0-16.0.beta.el7sat.noarch, tfm-rubygem-katello-3.4.4-1.el7sat.noarch

- created a CV with filter to exclude some errata, published the CV
- register host to the CV/env
- 'yum update' the host so that it is 'up to date'

- with Settings -> Content -> "Installable errata from Content View" set to 'Yes', the host's status (from Hosts -> All Hosts -> click on host) is green - "All errata applied".  Setting it to 'No' makes it yellow/warning - "Non-security errata applicable".
Comment 5 Satellite Program 2018-02-21 16:51:07 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.