Project

General

Profile

Actions
Copy link

Bug #20513

closed

Sometimes the webapp fails to generate the reporting file of new techniques

Added by Félix DALLIDET almost 3 years ago. Updated almost 3 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
7.0.0~rc3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
124
Name check:
To do
Fix check:
To do
Regression:

Description

This breaks the generation status with the following errors:

root@server:/var/rudder/configuration-repository# ls techniques/ncf_techniques/My_other_technique/1.0/
metadata.xml  technique.cf  technique.json  technique.ps1  technique.rd


[2022-01-04 16:11:49+0100] INFO  policy.generation.manager - Successful policy update '5' [started 2022-01-04 16:11:47 - ended 2022-01-04 16:11:49]
[2022-01-04 16:16:31+0100] INFO  compliance - [metrics] global compliance (number of components): undefined
[2022-01-04 16:17:49+0100] WARN  com.normation.appconfig.GenericConfigService - Error when trying the read rudderc targets from settings (using default: cfengine): (Accumulated: Inconsistency: (expected '"' got 'c'))
[2022-01-04 16:17:51+0100] INFO  techniques.reader - Reloading technique library, found modified technique(s): ['My_other_technique': updated (1.0: added)]
[2022-01-04 16:17:51+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'My_other_technique' in category 'User Techniques (ncf_techniques)' of active techniques library
[2022-01-04 16:17:51+0100] INFO  com.normation.rudder.services.policies.DeployOnTechniqueCallback - Update Technique library after creating files for ncf Technique My other technique
[2022-01-04 16:17:51+0100] INFO  policy.generation - Start policy generation, checking updated rules
[2022-01-04 16:17:51+0100] INFO  policy.generation - [metrics] Xmx:1015 MB nodes:2 (cached:2) rules:4 (enabled:3) techniques:47 (enabled:47) directives:8 (enabled:8) groups:2 (dynamic:2) parameters:2
[2022-01-04 16:17:51+0100] INFO  policy.generation - No node configuration was updated, no policies to write
[2022-01-04 16:17:51+0100] DEBUG explain_compliance - Updated node configuration ids:
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Timing summary:
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Run pre-gen scripts hooks     :          2 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Run pre-gen modules hooks     :          0 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Fetch all information         :        121 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Build current rule values     :          2 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Build target configuration    :         20 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Write node configurations     :        391 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Save expected reports         :          0 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Run post generation hooks     :        425 ms
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Number of nodes updated       :          0
[2022-01-04 16:17:52+0100] INFO  policy.generation.timing - Policy generation succeeded in:        1 s
[2022-01-04 16:17:52+0100] INFO  policy.generation.manager - Successful policy update '6' [started 2022-01-04 16:17:51 - ended 2022-01-04 16:17:52]
[2022-01-04 16:18:07+0100] INFO  policy.generation - Start policy generation, checking updated rules
[2022-01-04 16:18:07+0100] INFO  policy.generation - [metrics] Xmx:1015 MB nodes:2 (cached:2) rules:4 (enabled:4) techniques:47 (enabled:47) directives:9 (enabled:9) groups:2 (dynamic:2) parameters:2
[2022-01-04 16:18:08+0100] INFO  policy.generation - Configuration of 2 nodes were updated, their policies are going to be written
[2022-01-04 16:18:08+0100] DEBUG explain_compliance - Updated node configuration ids: [root:20220104-161147-ba4207ef->20220104-161807-18d0610][ea1ca98e-9605-45a8-9822-5c4b51505803:20220104-160950-1d40c1cb->20220104-161807-2dcd3698]
[2022-01-04 16:18:08+0100] ERROR com.normation.cfclerk.services.impl.GitTechniqueReader - Template with id techniques/ncf_techniques/My_other_technique/1.0/rudder_reporting.cf was not found
[2022-01-04 16:18:08+0100] INFO  policy.generation.timing - Policy generation failed after:
[2022-01-04 16:18:08+0100] ERROR policy.generation.manager - Error when updating policy, reason was: Cannot write nodes configuration; cause was: Unexpected: Accumulated: Unexpected: Error when trying to open resource 'techniques/ncf_techniques/My_other_technique/1.0/rudder_reporting.cf'. Check that the file exists is correctly commited in Git, or that the metadata for the technique are corrects.
[2022-01-04 16:18:08+0100] ERROR policy.generation.manager - Policy update error for process '7' at 2022-01-04 16:18:08: Cannot write nodes configuration; cause was: Unexpected: Accumulated: Unexpected: Error when trying to open resource 'techniques/ncf_techniques/My_other_technique/1.0/rudder_reporting.cf'. Check that the file exists is correctly commited in Git, or that the metadata for the technique are corrects.
[2022-01-04 16:21:33+0100] INFO  techniques.reader - Reloading technique library, no modified techniques found

The technique that broke the webapp is attached to the ticket.

Files

My_other_technique.json (1.6 KB) My_other_technique.json Félix DALLIDET, 2022-01-04 16:26
Actions
Copy link

Also available in: Atom PDF