Activity
From 2014-10-30 to 2014-10-30
2014-10-30
- 19:09 User story #5434 (Pending technical review): Change the frequency of the agent execution
- PR here: https://github.com/Normation/rudder/pull/654
- 17:41 User story #5717 (Pending technical review): Bump the doc version to 3.0
- PR is ready: https://github.com/Normation/rudder-doc/pull/78
- 17:27 User story #5717 (Released): Bump the doc version to 3.0
- The version is still 2.11 on the 3.0 doc, and requires an update.
- 17:36 Bug #5718: In reports list, if the directive contains < >, then the part in < > doesn't appear in the reports
- I think it's not correctly handled by datatable and filtered ...
- 17:35 Bug #5718 (Released): In reports list, if the directive contains < >, then the part in < > doesn't appear in the reports
- Since Rudder 2.11, if a directive contains < > in its name, this part doesn't appear in the Directive list of reports...
- 17:25 Bug #5716: Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
- ok, after a while (15 minutes apparently) it does reports current state (unexpected old reports)
i guess I'd like ... - 17:15 Bug #5716: Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
- This happens in non-compliance mode; and only as long as node don't send there new reports (i prevented my nodes from...
- 17:09 Bug #5716: Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
- Here, there is the configuration and reports of directives in a directive
there is one less directives in the report... - 17:05 Bug #5716 (Rejected): Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
- Randomly, there are missing Directives or Nodes in the Rules details
Didn't find the cause yet, but it seems some ... - 16:52 User story #5715 (Released): Rudder rudder-server-relay package (integration)
- Please see the upper ticket for details.
- 16:16 Bug #5714 (Released): Compliance percents are not sorted correctly
- You can click on the compliance heading to sort descending or ascending by the compliance percentage.
But it has a n... - 12:34 Bug #5713 (Rejected): Compliance shows "Rrepaired:" rather than "Repaired: xy%" in the graphs
- Compliance in the rule table shows "Rrepaired:" rather than the proper value
- 11:38 Bug #5712: Defining long classes (about > 2064 char) in CFEngine causes segfault
- Related issue https://dev.cfengine.com/issues/6719
- 10:51 Bug #5712 (Rejected): Defining long classes (about > 2064 char) in CFEngine causes segfault
- When we define large class with CFEngine, it may segfault (both in CFEngine 3.5 and 3.6), or bus error, killing the a...
- 10:49 Bug #5681 (Pending technical review): Technique "SSH keys distribution" 2.0 - adding large number of keys breaks the policy generation
- https://github.com/Normation/rudder-techniques/pull/552
- 10:20 Bug #5681: Technique "SSH keys distribution" 2.0 - adding large number of keys breaks the policy generation
- I can definitively reproduce the issue
If the key is too long ( roughly around the 1K length, then the class definit... - 10:48 Revision 57907a54 (rudder-techniques): Fixes #5681: change class definition in ssh_key_distribution to prevent segfault
- 10:17 Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for ever
- ok, i'm able to reproduce the issue; it's the class definition that fails.
The ticket for the Segfault issue is http... - 00:46 Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for ever
- This is apparently triggered by the length of the key.
wc -c .ssh/id_rsa.pub
737 .ssh/id_rsa.pub -> is OK
wc ... - 00:34 Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for ever
- replacing the existing key with random text made it not dump core.
number of lines also didn't matter.
Content is... - 00:17 Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for ever
- Florian Heigl wrote:
> I applied the same update (server and agents) on the second lab now, getting coredumps there!... - 00:15 Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for ever
- [Comment has been removed as the author requested it, due to confidential information.]
Also available in: Atom