Bug 2077811

Summary: new host ui, content, errata subtab, when N/A is chosen as severity filter erratas results are empty
Product: Red Hat Satellite Reporter: tstrych
Component: Hosts - ContentAssignee: Lucy Fu <lufu>
Status: CLOSED ERRATA QA Contact: Peter Dragun <pdragun>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: lufu, zhunting
Target Milestone: 6.12.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-16 13:33:46 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:

Description tstrych 2022-04-22 09:58:37 UTC 
Description of problem:
SSIA
2 attached screenshots one is listing an erratas with no filter and the second one shows the described problem, no erratas shown when N/A selected.  


Version-Release number of selected component (if applicable):
sat 6.11 snap 14

How reproducible:
Always

Steps to Reproduce:
1. register a host to activation key with the content view that contains a package with errata
2. install the package
3. open the new host UI, content tab, errata sub tab, choose severity filter N/A 

Actual results:
filtering severity by N/A doesn't work

Expected results:
Possible solutions:
the severity filter will no longer support N/A option 
or the filter will work correctly. 
Of course preferably the latter. 

Additional info:
I can provide a reproducer if needed, can be problematic to create N/A severity errata. 

The answer from the developer, the explanation and the workaround. 
N/A is stored as 'None' in the actual errata metadata, so I think you'd have to search for 'severity = None'. The autocomplete should help with this.
Comment 4 Lucy Fu 2022-07-25 21:35:46 UTC 
Created redmine issue https://projects.theforeman.org/issues/35277 from this bug
Comment 5 Bryan Kearney 2022-07-26 00:04:34 UTC 
Upstream bug assigned to lufu
Comment 6 Bryan Kearney 2022-07-26 00:04:36 UTC 
Upstream bug assigned to lufu
Comment 7 Bryan Kearney 2022-08-02 12:04:37 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35277 has been resolved.
Comment 9 Zach Huntington-Meath 2022-08-16 12:24:13 UTC 
flagged by mistake
Comment 10 Lucy Fu 2022-08-16 14:45:43 UTC 
https://gitlab.cee.redhat.com/satellite/katello/-/merge_requests/1025
Comment 11 Peter Dragun 2022-08-19 11:23:01 UTC 
Verified on Sat 6.12 snap 7. After using a filter with severity on N/A I am able to see errata as expected.
Comment 15 errata-xmlrpc 2022-11-16 13:33:46 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 (Important: Satellite 6.12 Release), 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-2022:8506