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:
Installable errata from Content View setting must be set to True
Version-Release number of selected component (if applicable):
Satellite 6.13
How reproducible:
100%
Steps to Reproduce:
1. Check the "Installable errata from content view" setting from the Administer > Settings > Content tab which is set to False
Actual results:
Installable errata from content view setting is set to False by default
Expected results:
As an end-user, this is an important setting to report the correct errata that a host is missing otherwise it would be misleading on the number of errata that is shown for each content host.
Additional info:
Hello Brad,
"No" is the default setting in previous versions of Satellite as well, we have to manually turn it on for the errata reporting to be correct.
Turns out that this setting is about whether to base your host's errata status on installable or applicable errata. I'm updating the setting's full name and description so that others don't have to wonder. However, I don't think it'd be wise to change the default value of this setting for all users. I think basing the host errata status on applicable errata is what most users expect, and changing defaults shouldn't be done lightly.
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.13 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-2023:2097