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.
This bug was initially created as a copy of Bug #2154184
Satellite is not able to detect when a setting changes from a non-default to
default value and if such a change happens, it continues using the non-default
one until services are restarted. This affects all releases from 6.11 onwards.
Steps to reproduce:
1) Run rails console
2) Pick a $setting without custom value
3) Read a value of $setting with Setting[$setting]
4) In another process, change the value of $setting to a non-default one
5) Reload the settings with Foreman.settings.load_values
6) Repeat 3, notice the value is what was set in 4
6) In another process, change the value of $setting to the default one
7) Repeat 5
8) Repeat 3
Actual results:
The value in 8 is the same as in 6
Expected results:
The value in 8 is the same as in 3
Verified.
Version Tested: Satellite 6.13 Snap 11.0
Verification steps:
1) Run rails console
2) Pick a $setting without custom value ==> picked 'allow_auto_inventory_upload'
3) Read a value of $setting with Setting[$setting] ==> true
4) In another process, change the value of $setting to a non-default one ==> setting to false
5) Reload the settings with Foreman.settings.load_values ==> running Foreman.settings.load_values
6a) Repeat 3, notice the value is what was set in 4 ==> it is false indeed
6b) In another process, change the value of $setting to the default one ==> moved it back to true
7) Repeat 5 ==> running Foreman.settings.load_values
8) Repeat 3 ==> true
and got the expected result: The value in 8 is the same as in 3 (true)
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
A hotfix RPM is available for Satellite 6.12.4. It is too large to be provided as a bugzilla attachment; please open a case with Red Hat Support to request the hotfix RPM if you require it.