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.

Bug 2165952

Summary: Warning: Setting puppet_<variable> has no definition, please define it before using
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: DashboardAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.0CC: ahumbe, aruzicka
Target Milestone: 6.13.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-3.5.1.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:24:53 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 Lukáš Hellebrandt 2023-01-31 15:01:07 UTC 
Description of problem:
When displaying dashboard in WebUI, I get the following warnings in the production.log, however I haven't noticed anything broken:

```
2023-01-31T09:14:31 [I|app|4e163ef2] Started GET "/widgets/77" for <IP> at 2023-01-31 09:14:31 -0500
2023-01-31T09:14:32 [I|app|4e163ef2] Processing by DashboardController#show as HTML
2023-01-31T09:14:32 [I|app|4e163ef2]   Parameters: {"id"=>"77"}
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_interval has no definition, please define it before using
2023-01-31T09:14:32 [W|app|4e163ef2] Setting puppet_out_of_sync_disabled has no definition, please define it before using
2023-01-31T09:14:32 [I|app|4e163ef2] Completed 200 OK in 390ms (Views: 161.2ms | ActiveRecord: 58.2ms | Allocations: 56679)
```

Version-Release number of selected component (if applicable):
Sat 6.13 snap 7.0 and NOT 6.12.0 => Regression

How reproducible:
Deterministic

Steps to Reproduce:
1. Login to Satellite's WebUI and watch production.log when accessing dashboard

Actual results:
Warnings in log

Expected results:
No warnings in log
Comment 2 Lukáš Hellebrandt 2023-02-28 14:46:07 UTC 
Verified with Sat 6.13.0 snap 12.0

Accessing dashboard now doesn't produce the above warnings and everything seems to work.
Comment 5 errata-xmlrpc 2023-05-03 13:24:53 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