Rudder

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,

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

Attached another screenshot, unexpected.png.

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

PR

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

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

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

Benoît,

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

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

Applied in changeset rudder-techniques|cea2e17aac1a295043a65fd2912a920f887a9014.

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

• Announcement 3.0
• Changelog 3.0
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/