Project

General

Profile

Actions

Bug #12347

closed

Handle errata status with Library vs current environment

Added by Justin Sherrill about 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Category:
Errata Management
Target version:
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

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.

So it may make sense to have two different errata statuses:

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.


Related issues 1 (1 open0 closed)

Blocks Katello - Feature #11435: Host Unification TrackerNewActions
Actions

Also available in: Atom PDF