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.

Bug 1146878

Summary: Applicable Errata on Hosts not visible and separate list of Errata availability in Content Views
Product: Red Hat Satellite Reporter: Peter Vreman <peter.vreman>
Component: WebUIAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED NEXTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: asogukpi, bkearney, nstrug, walden
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 15:43:24 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1122832, 1130651    
Attachments:
Description Flags
dashboard.PNG
none
errata.PNG
none
content.PNG none

Description Peter Vreman 2014-09-26 09:56:11 UTC
Description of problem:
There is not way to see which hosts are affected by an errata. The Content Dashboard widget "Errata Overview" does list the amount of affected Content Hosts: e.g. RHSA-2014:1293 (6 Content Hosts)
But clicking on the link will goto to Content Saerch and then only report in which content views the Errata is included.

Please extend the applicable Errata overview:
- Out of date Hosts compared with their Content views
- Out of date Content Views compared with the Errata in the "Default Content View" after synchronizing with RedHatNetwork


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2014-09-26 10:03:28 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.

Comment 3 Nick Strugnell 2014-10-08 09:40:31 UTC
To expand on this, please see the attached screenshots for an example of this behaviour.

We currently have multiple servers that have outstanding errata. The errata have been added into the content view and the content view has been published.

Logging into the "Content Dashboard", there is no obvious indication that critical errata are available for hosts, see attachment dashboard.PNG. This shows a large green status indicator - which is actually for subscriptions rather than for the rather more important patch status.

Scrolling down, we see an indicator box which is off the bottom of the screen (on a normal sized laptop). See attachment errata.PNG. This clearly shows that 24 Content Hosts have a security errata outstanding.

Clicking on the first link one might reasonably expect to be taken to a screen where the 24 vulnerable hosts are listed, however this is not the case, instead we see the screen shown in attachment content.PNG.

This screen is confusing. There are no references to any hosts or errata. On further investigation, it is simply the results of a content search indicating which content views contain this errata - this is not useful information, I just added the errata to the content views so I am well aware of this.

Unless I am completely missing something, there is no clear way of seeing to which hosts the erratum is applicable, and from there, applying it.

This is a serious regression from satellite 5 which made such operations simple and what is more, indicated the current patch state of hosts with clear colour-coded symbology.

The current focus of katello seems to be on subscription status which is frankly of minor concern to customers in comparison to patch status.

Comment 4 Nick Strugnell 2014-10-08 09:41:37 UTC
Created attachment 944891 [details]
dashboard.PNG

Comment 5 Nick Strugnell 2014-10-08 09:42:06 UTC
Created attachment 944892 [details]
errata.PNG

Comment 6 Nick Strugnell 2014-10-08 09:42:33 UTC
Created attachment 944894 [details]
content.PNG

Comment 7 Walden Raines 2015-02-19 15:43:24 UTC
This is addressed with the Errata Management feature of Satellite 6.1