Bug #6311: Missing reports when editing twice the same file with enforce a file content v7.0 - Rudder - Issue Tracker

Actions

Copy link

Bug #6311

closed

Bug #6343: When a technique reports several time the exact same text, there is only one report generated

Missing reports when editing twice the same file with enforce a file content v7.0

Added by Dennis Cabooter almost 10 years ago. Updated over 9 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

Web - Config management

Target version:

3.0.4

Pull Request:

https://github.com/Normation/rudder-t...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

I created a new directive + rule and the status is reported as Unknown, while the technical logs are actually there. Don't know how to debug this.

See attached screenshot.

Files

Download all files

no_report.png (34.4 KB) no_report.png		Dennis Cabooter, 2015-03-02 10:22
tech_logs.png (202 KB) tech_logs.png		Dennis Cabooter, 2015-03-02 10:22
reports.png (55.2 KB) reports.png		Dennis Cabooter, 2015-03-02 11:09
unexpected.png (73.6 KB) unexpected.png		Dennis Cabooter, 2015-03-02 14:42

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by François ARMAND almost 10 years ago

Category set to Web - Config management
Assignee set to François ARMAND

Hello Denis,

Unknown reports mean that Rudder get reports, but that they were not expected for that node at that moment. For example, Rudder was not waiting for reports from the given technique, or the reports are coming with a bad revision number, or a too old version.

That may happen if the node clock and the server are out of sync, if the node didn't correctly got its promises (and so report on old one), or other strange edge caeses.

How to debug:

- first, the developper MUST PUT THE EXPECTED REPORT VERSION SOMEWHERE IN THE INTERFACE. Bad developpers => http://www.rudder-project.org/redmine/issues/6313
- second, you can check that the revision number for the node is the same in the promise generated by Rudder than in the log_info sent by the node:
In Rudder, go to /var/rudder/share/${nodeid}rules/cfengine-community/common/1.0/site.cf and search for "rudder_node_config_id" string => "xxxx";. Compare to the number for the node in the technical log, for the log with level "log_info" and value "endRun" (filtering for endRun should be ufficient). The message for that log is: End execution with config [xxxx]. The two value should be identical.
- third, we have a verbose mode for logging report analysis, that explains what Rudder get, how it interprets it, and what it does with it. To enable it, you must edit the file /opt/rudder/etc/logback.xml and change the line (near the end): <logger name="explain_compliance", change level to: level="debug" and restart Rudder.

Hope it helps,

Actions

Copy link

Updated by Dennis Cabooter almost 10 years ago

Did I already mention all the nodes which have the new/rule directive have the same No Report for that particular rule?

Actions

Copy link

Updated by Dennis Cabooter almost 10 years ago

File reports.png reports.png added

Here another screenshot. The reports in the attachement are the same on both nodes in the group.

Actions

Copy link

Updated by Dennis Cabooter almost 10 years ago

I don't see anything strange in the logs, not even with debug level on.

Actions

Copy link

Updated by Dennis Cabooter almost 10 years ago

File unexpected.png unexpected.png added

Attached another screenshot, unexpected.png.

Actions

Copy link

Updated by Nicolas CHARLES almost 10 years ago

Ok, the issue is that the Directive edits twice the same file. However, the agent doesn't report duplicate the reports, so it send one message only per file, causing the unexpected or missing report. I could reproduce the issue in 3.0
Dennis thinks it used to work in 2.11, i'll check it there

Actions

Copy link

Updated by Nicolas CHARLES almost 10 years ago

Subject changed from Unknown reports but technical logs are there to Missing reports when editing twice the same file with enforce a file content v7.0
Status changed from New to 8
Assignee changed from François ARMAND to Benoît PECCATTE

Ok, the issue is on enforce a file content v7.0; using v6.0 fixes the issue ...

Actions

Copy link

Updated by Benoît PECCATTE almost 10 years ago

Status changed from 8 to Pending technical review
Assignee changed from Benoît PECCATTE to Nicolas CHARLES

Actions

Copy link

Updated by Benoît PECCATTE almost 10 years ago

Pull Request set to https://github.com/Normation/ncf/pull/175

PR https://github.com/Normation/ncf/pull/175

Actions

Copy link

#10

Updated by Benoît PECCATTE almost 10 years ago

Pull Request changed from https://github.com/Normation/ncf/pull/175 to https://github.com/Normation/rudder-techniques/pull/638

Sorry, PR HERE https://github.com/Normation/rudder-techniques/pull/638

Actions

Copy link

#11

Updated by Nicolas CHARLES almost 10 years ago

Parent task set to #6343

Actions

Copy link

#12

Updated by Vincent MEMBRÉ almost 10 years ago

Target version changed from 3.0.2 to 3.0.3

Actions

Copy link

#13

Updated by Nicolas CHARLES almost 10 years ago

Reproduced set to No

i'm not really happy with this solution, as we are including numbers wihtout meaning for the user in text
I'd really prefer to have the index added as a parameter of the bundle, and used as a comment, to ensure differences of bundle calls, and without polluting the reporting

Actions

Copy link

#14