Project

General

Profile

Actions

Bug #25912

closed

First run after node acceptance does not send reports

Added by Nicolas CHARLES about 1 month ago. Updated 19 days ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:
No

Description

I accepted a node, and the first run did not send reports, as the agent believed (wrongly) it was in initial policies

root@mgmt:/home/vagrant# rudder agent run -I
Rudder agent 8.2.2~git202411192205
Node uuid: 42c4c9b4-99ef-4c82-9c23-592d843f66f3
ok: Rudder agent policies were updated.
Start execution with config [20241120-110101-3f12de3f]

2024-11-20T10:49:16+00:00 R: [INFO] Starting CFEngine 3.21.5a.cb2b5dcb4 on host mgmt.rudder.local (debian_11 x86_64)
M| State         Technique                 Component                 Key                Message
E| compliant     Common                    ncf Initialization                           Configuration library initialization was correct
   info          Common                    Update                                       Local configuration library updated
   info          Common                    Update                                       Configuration policy updated
E| repaired      Common                    Update                                       Policy or configuration library were updated
E| compliant     Common                    Security parameters                          The internal environment security is acceptable

## Summary #####################################################################
664 components verified in 5 directives
   => 338 components in Enforce mode
      -> 32 compliant
      -> 1 repaired
      -> 296 not-applicable
      -> 9 error
   => 326 components in Audit mode
      -> 120 compliant
      -> 32 not-applicable
      -> 174 non-compliant
Execution time: 20.62s
################################################################################
info: initial policies, skipping reporting

as a result, i don't know what happened during first run
Happens in 8.2, likely in 8.1 also


Subtasks 1 (0 open1 closed)

Bug #25990: First run after node acceptance does not send reports - bug in parentReleasedFélix DALLIDETActions
Actions

Also available in: Atom PDF