Bug 1368254

Summary:	Handle errata status with Library vs current environment
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Errata Management	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, bkearney, brubisch, chrobert, cpatters, egolov, ggatward, jcallaha, lpramuk, mjahangi, mmello, nitthoma, oshtaier, pdwyer, pwaghmar, rbobek, rplevka, swadeley, yann.lopez, zhunting
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
URL:	http://projects.theforeman.org/issues/12347
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.0.0.86-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1394360 (view as bug list)		Environment:
Last Closed:	2016-12-12 17:13:00 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:
Bug Depends On:
Bug Blocks:	1394360

Description Nagoor Shaik 2016-08-18 20:33:40 UTC

Description of problem:
Currently the errata only looks at all applicable errata, and does not handle 'installable errata'

Some users may only care about installable errata, and it may be useful to query based on installable errata status.

Version-Release number of selected component (if applicable):
Satellite 6.2.1

How reproducible:
100%

Steps to Reproduce:
1. Create a Content View and register a client to that specific content-view
2. Patch the system fully 
3. Check the over all status of the host which shows "Error" and the Errata status shows "Security errata applicable"

Actual results:
Overall status shows Error, even in case of a fully patched system (where no installable errat

Expected results:
So it may make sense to have two different errata status:

installable errata
applicable errata

each with security/non_security/none states

And the user could decide (via a setting) whether or not to use each one to build the global status.

Additional info:

Comment 3 Chris Roberts 2016-10-04 21:31:54 UTC

*** Bug 1376224 has been marked as a duplicate of this bug. ***

Comment 4 Bryan Kearney 2016-10-12 22:02:27 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 6 Roman Plevka 2016-12-07 12:19:20 UTC

VERIFIED

# rpm -qa satellite
satellite-6.2.5-1.0.el7sat.noarch

- created a CV with filter to exclude some errata.
- subscribed host
- got an applicable errata.

- with settings -> katello -> errata_status_installable set to TRUE,
the host's status is green - "All errata applied".
Setting it to 'FALSE' makes it a warning.

Comment 7 errata-xmlrpc 2016-12-12 17:13:00 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/RHBA-2016:2940

Comment 8 Kathryn Dixon 2017-07-11 22:46:51 UTC

*** Bug 1372840 has been marked as a duplicate of this bug. ***