Architecture #27480: Reports from one report may leak to another report - Rudder - Issue Tracker

Actions

Copy link

Architecture #27480

open

Reports from one report may leak to another report

Added by Nicolas CHARLES 25 days ago. Updated 23 days ago.

Status:

New

Priority:

Assignee:

Alexis Mousset

Category:

Agent

Target version:

Ideas (not version specific)

Pull Request:

Effort required:

Name check:

To do

Fix check:

To do

Regression:

Description

With an agent in change only report, commands report may leak to other report

2025-06-16T16:29:01+00:00   notice: Q: "...rpm -q gpg-pubk": gpg-pubkey-aaaaaa
2025-06-16T16:29:02+00:00   notice: Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa1_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa2_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa3_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa4_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa5_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa6_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa7_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa8_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa9_present
2025-06-16T16:29:02+00:00 Q: ".../bin/rpm -q gpg": +hook_repo_gpg_key_aaaaaa10_present
2025-06-16T16:29:02+00:00 R: Condition sysctl_reload_false defined
2025-06-16T16:29:02+00:00    error: Only functions returning scalars can be used as arguments
2025-06-16T16:29:03+00:00    error: Only functions returning scalars can be used as arguments
2025-06-16T16:29:03+00:00    error: Only functions returning scalars can be used as arguments
2025-06-16T16:29:03+00:00 R: @@file_custom_dns_server_for_host@@log_repaired@@AAAAAAAAAAAA@@BBBBBBBBBBBBBBBB@@aCCCCCCCCCCCCC@@File from a jinja2 template@@/path/to/file~@@2025-06-16 16:29:00+00:00##ZZZZZZZZZZZZZZZZZZZ@#Remove file /var/rudder/cfengine-community/inputs/file_custom_dns_server_for_host/1.0/resources/file.j2.datastate.6596.json was repaired

result in the gpg report being attached in the technical log to the jinja2 reports
It might be in the agent, or in the compliance part

Actions

Copy link

Updated by Nicolas CHARLES 25 days ago

Priority changed from N/A to To review

Actions

Copy link

Updated by François ARMAND 23 days ago

Tracker changed from Bug to Architecture
Priority changed from To review to 4
Priority deleted (0)

So, this is complicated because we don't have the info that we are in change only AND we don't have structured reports.

We can act at relayd level by skipping the log report (skip_event_types config parameter in relayd config file).

The real correction of that is a big change in report structure so that they are structured and we can attach correctly leaf to their roots, and not try to guess which one is what.

Actions

Copy link