Project

General

Profile

Actions

Bug #27480

open

Reports from one report may leak to another report

Added by Nicolas CHARLES about 10 hours ago. Updated about 10 hours ago.

Status:
New
Priority:
To review
Assignee:
-
Category:
Agent
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

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 #1

Updated by Nicolas CHARLES about 10 hours ago

  • Priority changed from N/A to To review
Actions

Also available in: Atom PDF