Bug 2168168

Summary:	Installable errata from Content View setting must be set to True
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Errata Management	Assignee:	Jeremy Lenz <jlenz>
Status:	CLOSED ERRATA	QA Contact:	Samir Jha <sajha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.13.0	CC:	ahumbe, iballou, jlenz, pcreech, sajha, zhunting
Target Milestone:	6.13.0	Keywords:	EasyFix, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.7.0.12-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:24:54 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 Nagoor Shaik 2023-02-08 11:04:08 UTC

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:

Comment 1 Brad Buckingham 2023-02-09 15:22:42 UTC

Is this a regression from Satellite 6.12?  Thanks!

Comment 2 Nagoor Shaik 2023-02-13 03:42:43 UTC

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.

Comment 3 Ian Ballou 2023-02-15 17:52:09 UTC

This sounds like a good idea at a glance. Would be very easy to fix.

Comment 4 Jeremy Lenz 2023-02-17 15:33:12 UTC

Created redmine issue https://projects.theforeman.org/issues/36124 from this bug

Comment 5 Jeremy Lenz 2023-02-17 15:40:46 UTC

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.

Comment 6 Bryan Kearney 2023-02-17 16:03:42 UTC

Upstream bug assigned to jlenz

Comment 7 Bryan Kearney 2023-02-17 16:03:44 UTC

Upstream bug assigned to jlenz

Comment 8 Jeremy Lenz 2023-02-20 15:53:01 UTC

To verify: 

Only verify that the setting description and wording changed (we didn't change the default value.)

Comment 13 errata-xmlrpc 2023-05-03 13:24:54 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.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