Bug #6419
closed
Command execution generic method does not send compliance report because rudder_expected_reports.csv is empty
Added by François ARMAND over 9 years ago.
Updated over 9 years ago.
Category:
Web - Technique editor
Description
when using the "command execution" generic method to build a technique, the corresponding report is missing as shown in screenshot.
On the agent side, a "rudder agent run" says:
root@agent1:/home/vagrant# rudder agent run
R: @Common@log_info@hasPolicyServer-root@common-root@4@common@StartRun@2015-03-17 11:42:38+00:00##035f8d52-8182-41d4-a582-4bacbebab39b@#Start execution with config [-1898320997]
....[other techniques]...
2015-03-17T11:42:38+0000 notice: /default/Exec__bin_date/methods/'method_call'/default/command_execution/commands/'/bin/date'[0]: Q: ".../bin/date": Tue Mar 17 11:42:38 UTC 2015
....[other techniques]...
R: @Common@log_info@hasPolicyServer-root@common-root@4@common@EndRun@2015-03-17 11:42:38+00:00##035f8d52-8182-41d4-a582-4bacbebab39b@#End execution with config [-1898320997]
Files
- Subject changed from Command execution generic method does not send compliance report to Command execution generic method does not send compliance report because rudder_expected_reports.csv is empty
With more checking we found that:
root@server:/var/rudder/share/035f8d52-8182-41d4-a582-4bacbebab39b/rules/cfengine-community# ls la
...
-rw------ 1 root root 0 Mar 17 12:07 rudder_expected_reports.csv
Some more fun:
- the file /var/rudder/configuration-repository/techniques/ncf_techniques/Exec_cmd_2/1.0/expected_reports.csv has the expected contents,
- addind an empty line to that file, reloading techniques and then on nodes, "rudder agent update" leads to having the correct, non empty file on the node,
- removing the empty line on the server (and reloading techniques and updating promises on nodes) DOES NOT go back to the initial behaviour (and so, still works).
When reports starts to comes, it seems that we can't make them disapear again and so that we must create a new technique from technique editor to see the bug again.
Some more digging make appears that the technique descriptor, as seen by Rudder, does not provide reports. So the problem lies on the way providesExpectedReports is filled.
- Status changed from New to Pending technical review
- Assignee set to Nicolas CHARLES
- Priority changed from N/A to 2
- Target version set to 3.0.3
- Pull Request set to https://github.com/Normation/cf-clerk/pull/71
OK, so state are EVIL. Don't use them, it hurts.
Only on 3.0.x
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset cf-clerk|commit:9a6914d364895699cd9768040a21bd3d12f192e1.
Applied in changeset cf-clerk|commit:2bc4a7be031357e8bf3d95486cde4996a83e0234.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.3 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
