Bug 2069797
| Summary: | foreman throws hundreds of puppetrun errors per host if puppet_proxy yml files exist | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jessica Richards <jrichards2> |
| Component: | Puppet | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.10.2 | CC: | casl, jcrumple, myoder, nalfassi, vsedmik, wpinheir |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-30 12:43:21 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
Jessica Richards
2022-03-29 17:44:50 UTC
Follow-up: After further testing, I've found that my workaround (mentioned in the problem description, and also below) is not, in fact, a reliable fix: 1. move the puppet_proxy files in /etc/foreman-proxy/ to another location 2. run "satellite-installer" 3. reboot I have been able to reproduce this issue easily just by registering my content host to a Satellite 6.10 server.
I've done a little investigating, and I see the error is thrown from this file, from the SettingRegistry class:
~~~
/usr/share/foreman/app/services/setting_registry.rb
~~~
We see the definition is getting assigned here, by seeing if the name "puppetrun" exists in the settings table from the foreman db:
~~~
16 def find(name)
17 logger.warn("Setting is not initialized yet, requested value for #{name} will be always nil") unless ready?
18 @settings[name.to_s]
19 end
~~~
I can see that Satellite 6.8 does have the puppetrun entry in the foreman settings table, but 6.9 and 6.10 do not. Only Satellite 6.10 throws this error, while Satellite 6.9 does not.
Further, I think this wasn't caught until the SettingRegistry class was introduced, which appears to have been added in Satellite 6.10. Since seeing this bug, I have seen this issue appear in multiple customer environments (usually heavily logged since each host is triggering this).
I'm not exactly sure where the value of puppetrun is getting introduced (i.e. the rhsm libraries from the content host, or somewhere still from the Satellite server). Is there any way we can disable this feature, to prevent all of these WARN logging messages?
Kind regards,
Puppetrun was removed from 6.9 and later versions (see https://bugzilla.redhat.com/show_bug.cgi?id=1905096), so there shouldn't be any way how to disable something what should be missing. Strange that this bug manifests in 6.10 and not in 6.9. This seems to no longer be occurring with 6.10. After thorough testing and analysis on Satellite 6.13, I regret to inform you that I was unable to reproduce the issue as described in the ticket. Despite following the provided steps, the issue could not be replicated. As a result, I am closing the BZ ticket. However, please note that if the issue reoccurs or if additional information becomes available, we can reopen the ticket for further investigation. |