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.
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.
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