[AAP-77542] - Make receptor_log_level configurable for mesh ingress pods#2118
Open
demonpig wants to merge 1 commit into
Open
[AAP-77542] - Make receptor_log_level configurable for mesh ingress pods#2118demonpig wants to merge 1 commit into
demonpig wants to merge 1 commit into
Conversation
Mesh ingress receptor pods previously hardcoded log-level to debug, flooding logs with routing advertisements and service discovery messages that could not be suppressed through the AutomationController CR's receptor_log_level field. This caused operational issues in production environments where debug-level logging generates excessive log volume. The mesh_ingress role now inherits receptor_log_level from the parent AWX CR spec (via the existing awx_spec lookup), matching the pattern used for control_plane_ee_image and image_pull_policy. This allows operators to control mesh ingress log verbosity through the same mechanism used for controller pods, while preserving backward compatibility by defaulting to debug. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: Max Mitschke <mmitschk@redhat.com>
demonpig
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SUMMARY
Make
receptor_log_levelconfigurable for mesh ingress pods by inheriting the value from the parent AutomationController CR'sreceptor_log_levelfield.Previously, the mesh_ingress role hardcoded
log-level: debugin the receptor ConfigMap template, causing all mesh ingress pods to emit DEBUG-level logs unconditionally. This flooded logs with routing advertisements and service discovery messages that could not be suppressed through the documentedreceptor_log_levelCR field, even when users explicitly set it toinfo,warning, orerror.The fix follows the existing pattern used in the installer role: the mesh_ingress role now extracts
receptor_log_levelfrom the parent AWX CR spec (via the existingawx_speclookup) and templates it into the receptor configuration. This ensures mesh ingress and controller pods can use the same log level setting while preserving backward compatibility by defaulting todebug.ISSUE TYPE
ADDITIONAL INFORMATION
Root cause:
- log-level: debug