Project

General

Profile

Actions

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 about 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
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

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 open1 closed)

Related to Rudder - User story #6313: Rudder 3.0 node info misses the "current report version identifier"RejectedFrançois ARMAND2015-03-02Actions
Actions #1

Updated by François ARMAND about 9 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 #2

Updated by Dennis Cabooter about 9 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 #3

Updated by Dennis Cabooter about 9 years ago

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

Actions #4

Updated by Dennis Cabooter about 9 years ago

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

Actions #5

Updated by Dennis Cabooter about 9 years ago

Attached another screenshot, unexpected.png.

Actions #6

Updated by Nicolas CHARLES about 9 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 #7

Updated by Nicolas CHARLES about 9 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 #8

Updated by Benoît PECCATTE about 9 years ago

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

PR

Actions #9

Updated by Benoît PECCATTE about 9 years ago

  • Pull Request set to https://github.com/Normation/ncf/pull/175
Actions #10

Updated by Benoît PECCATTE about 9 years ago

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

Updated by Nicolas CHARLES about 9 years ago

  • Parent task set to #6343
Actions #12

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.0.2 to 3.0.3
Actions #13

Updated by Nicolas CHARLES about 9 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 #14

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.0.3 to 3.0.4
Actions #15

Updated by Nicolas CHARLES almost 9 years ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

Benoît,

Could you rework on this issue please ? The number in the text is clearly not optimal for the user

Actions #16

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
Actions #17

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #19

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.4 which was released today.

Actions

Also available in: Atom PDF