Activity
From 2017-02-10 to 2017-02-10
2017-02-10
- 18:04 Revision 0fb9d9cd (rudder): Fixes #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- 18:04 Revision 43cab768 (rudder): Fixes #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- 17:49 Bug #10171 (Pending technical review): If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- PR https://github.com/Normation/rudder/pull/1491
- 15:15 Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- Seems good to me.
- 15:10 Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- risk is: if insert into ruddersysevents is too long, and web interface is restarted, deletion never occurs, so we may...
- 15:08 Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- Suggested implementation
# get A max id of archivedruddersysevents
# get R min id of ruddersysevents
# get C max i... - 14:46 Bug #10171 (In progress): If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- 11:39 Bug #10171 (Released): If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
- Reports archiving happens by default every day.
It's a 3 steps procedure, with:
# reports insertion into archivedru... - 17:33 Revision ddcf04cd (rudder): Merge branch 'branches/rudder/4.1'
- 17:33 Revision da00b2c2 (rudder): Merge branch 'branches/rudder/4.1'
- 17:33 Revision 31f733c6 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:33 Revision d4f6f1ae (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:33 Bug #10173 (Pending release): Display of new "Display compliance and recent changes columns on rule summary" setting is broken
- Applied in changeset commit:rudder|5f75861ae08c17bb9e2fe0919604aae2ec536318.
- 16:22 Bug #10173 (Pending technical review): Display of new "Display compliance and recent changes columns on rule summary" setting is broken
- PR https://github.com/Normation/rudder/pull/1489
- 15:12 Bug #10173 (In progress): Display of new "Display compliance and recent changes columns on rule summary" setting is broken
- 15:12 Bug #10173 (Released): Display of new "Display compliance and recent changes columns on rule summary" setting is broken
- This new setting was added in 3.1 but we have changed the Settings page design in 4.0, so now, its style does not mat...
- 17:33 Revision 5e24ab6e (rudder): Merge branch 'bug_10173/display_of_new_display_compliance_and_recent_changes_columns_on_rule_summary_setting_is_broken_pr' into branches/rudder/4.0
- 17:33 Revision 00cb98be (rudder): Merge branch 'bug_10173/display_of_new_display_compliance_and_recent_changes_columns_on_rule_summary_setting_is_broken_pr' into branches/rudder/4.0
- 17:30 Revision a33f4cff (rudder): Merge branch 'branches/rudder/4.1'
- 17:30 Revision f6a0a100 (rudder): Merge branch 'branches/rudder/4.1'
- 17:30 Revision 4d7ab382 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:30 Revision 3e4e4f45 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:29 Bug #10177 (Pending release): Status dropdown's display is broken
- Applied in changeset commit:rudder|b125cb1c82425faf0455a7e721b4fc98287ad030.
- 16:57 Bug #10177 (Pending technical review): Status dropdown's display is broken
- PR https://github.com/Normation/rudder/pull/1490
- 16:35 Bug #10177 (In progress): Status dropdown's display is broken
- 16:35 Bug #10177 (Released): Status dropdown's display is broken
- Not really broken, but some of elements of the Status dropdown are larger than the menu size, so we cannot see them i...
- 17:29 Revision 8c803d33 (rudder): Merge branch 'bug_10177/status_dropdown_s_display_is_broken_pr' into branches/rudder/4.0
- 17:29 Revision 23b07116 (rudder): Merge branch 'bug_10177/status_dropdown_s_display_is_broken_pr' into branches/rudder/4.0
- 17:25 Revision 87e25a46 (rudder): Merge branch 'branches/rudder/4.1'
- 17:25 Revision 82004d98 (rudder): Merge branch 'branches/rudder/4.1'
- 17:24 Revision 0856f684 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:24 Revision 6aefba99 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:23 Revision 5a6b45a7 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 17:23 Revision c5a595f5 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 17:22 User story #7422 (Pending release): Node breakdown - show actual numbers
- Applied in changeset commit:rudder|76624528bedc46c9b926e5091009c1e9b9532800.
- 17:21 Revision b01edf43 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 17:21 Revision af90d55b (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 17:21 Revision 7f16db7d (rudder): Merge branch 'ust_7422/node_breakdown_show_actual_numbers_pr' into branches/rudder/3.1
- 17:21 Revision 8e74c4cb (rudder): Merge branch 'ust_7422/node_breakdown_show_actual_numbers_pr' into branches/rudder/3.1
- 17:13 Bug #10178 (Pending release): the shared-files directory is owned by root
- Applied in changeset commit:rudder-packages|12d4f283700d196eb4d585dc041f26c9356b61e8.
- 17:05 Bug #10178 (Pending technical review): the shared-files directory is owned by root
- PR https://github.com/Normation/rudder-packages/pull/1255
- 17:03 Bug #10178 (In progress): the shared-files directory is owned by root
- 17:02 Bug #10178 (Released): the shared-files directory is owned by root
- 17:11 Revision 12d4f283 (rudder-packages): Fixes #10178: the shared-files directory is owned by root
- 16:57 Revision bc55301b (rudder): Fixes #10177: Status dropdown's display is broken
- 16:57 Revision b125cb1c (rudder): Fixes #10177: Status dropdown's display is broken
- 16:32 Revision c48cb0b7 (rudder-plugins): Fixes #10176: Datasource are broken since changing duration from minutes to seconds
- 16:32 Revision c48cb0b7 (rudder-plugin-datasources): Fixes #10176: Datasource are broken since changing duration from minutes to seconds
- 16:31 User story #10081 (Pending release): Use rudder agent run as cfruncommand
- Applied in changeset commit:rudder-techniques|b45528142831bcef4a548a3749775e41e0bafb4c.
- 16:31 Revision 17b44f5b (rudder-techniques): Merge branch 'ust_10081/use_rudder_agent_run_as_cfruncommand_pr' into branches/rudder/4.1
- 16:26 Revision b4552814 (rudder-techniques): Fixes #10081: Use rudder agent run as cfruncommand
- 16:23 Bug #10175 (Released): Promise validation errors (cf-promises) are unreadable
- cf-promises output gets all line breaks removed, and is unreadable.
Maybe since using hooks? - 16:22 Revision 90a22ca8 (rudder): Fixes #10173: Display of new \"Display compliance and recent changes columns on rule summary\" setting is broken
- 16:22 Revision 5f75861a (rudder): Fixes #10173: Display of new \"Display compliance and recent changes columns on rule summary\" setting is broken
- 16:10 Bug #10165 (Rejected): Incomplete inventory for one node - race condition?
- So. I tested several case, try to meet the race condition spot, and never succeeded in doing so. Each time, everythin...
- 12:05 Bug #10165: Incomplete inventory for one node - race condition?
- In fact, we are already doing the correct thing:...
- 11:32 Bug #10165 (In progress): Incomplete inventory for one node - race condition?
- 11:06 Bug #10165: Incomplete inventory for one node - race condition?
- And that problem exists since the begining of times.
- 11:05 Bug #10165: Incomplete inventory for one node - race condition?
- It is exactly that: in "rudder-node-to-relay", we are creating the entry "nodeId=XXXX, ou=Nodes, cn=rudder-configurat...
- 10:58 Bug #10165: Incomplete inventory for one node - race condition?
- The problem is very likely running rudder-node-to-relay on a pending node.
- 16:03 Bug #10170 (Pending release): Broken dict_merge test
- Applied in changeset commit:4a31a2699885fbefebe76050313acc50116467c1.
- 15:49 Bug #10170 (Pending technical review): Broken dict_merge test
- PR https://github.com/Normation/ncf/pull/529
- 11:37 Bug #10170 (New): Broken dict_merge test
- 11:34 Bug #10170 (In progress): Broken dict_merge test
- 11:34 Bug #10170 (Released): Broken dict_merge test
- Not available in 3.6.
- 15:53 Bug #10174 (Released): Can not see details of pending node
- When we want to accept a new node, we can't open the detailled information about the node anymore.
Moreover (not ... - 15:49 Revision 4a31a269 (ncf): Fixes #10170: Broken dict_merge test
- 15:00 User story #10169: UI to define node properties
- Work in progess here: https://github.com/RaphaelGauthier/rudder/commit/e1cd0ec7404a822a1570f2a7a1fc314132dadc2e
- 14:47 User story #10169: UI to define node properties
- Work in progess here: https://github.com/RaphaelGauthier/rudder/commit/78bf96aa6765928968712dfbec66bd3699c6d01c
- 10:39 User story #10169 (In progress): UI to define node properties
- 10:17 User story #10169 (Released): UI to define node properties
- We need to modify the Node properties tab's UI to allow us to define node properties.
The UI will be based on the ... - 14:24 User story #10152 (Pending technical review): Missing async option in the doc
- PR https://github.com/Normation/rudder-doc/pull/283
- 11:43 User story #10172 (New): Run cf-promises on examples in the doc
- We should tag code blocks containing CFEngine code and run cf-promises on them
- 11:12 Revision 1ad51462 (rudder): Merge branch 'branches/rudder/4.1'
- 11:12 Revision fb10176b (rudder): Merge branch 'branches/rudder/4.1'
- 11:11 Revision e0c376ad (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 11:11 Revision ab44d658 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 10:52 Revision a0e9eac1 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 10:52 Revision 8707ca9c (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 10:45 Bug #10168 (Pending release): Deadlock with simultaneous generation and new reports
- Applied in changeset commit:rudder|47bdd2d4b70eb5832b9b9b88ad5d237983c14512.
- 01:40 Bug #10168 (Pending technical review): Deadlock with simultaneous generation and new reports
- PR https://github.com/Normation/rudder/pull/1488
- 00:56 Bug #10168 (Released): Deadlock with simultaneous generation and new reports
- We observed a case where a generation can't end.
It seems to be link to the call of "cachedCompliance.invalidate(... - 10:44 Revision 74cde6f7 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 10:44 Revision bedd2e3b (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 09:38 Revision 12083430 (rudder): Fixes #10168: Deadlock with simultaneous generation and new reports
- 09:38 Revision 47bdd2d4 (rudder): Fixes #10168: Deadlock with simultaneous generation and new reports
- 02:35 Revision 4b3cd619 (rudder): Merge branch 'branches/rudder/4.1'
- 02:35 Revision 04e1b7d9 (rudder): Merge branch 'branches/rudder/4.1'
- 02:33 Revision fea33acf (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 02:33 Revision d3d7edde (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 02:33 Revision 92557ff4 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 02:33 Revision f6793150 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 02:21 Revision c4ba9016 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 02:21 Revision 635985fd (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 02:21 Bug #10133 (Pending release): Included "time ended" in Status dropdown
- Applied in changeset commit:rudder|b66ead5c3ba6b439a686ccba59f1a6e541eb1b5a.
- 02:21 Revision ae8e908a (rudder): Merge branch 'bug_10133/included_time_ended_in_status_dropdown_pr' into branches/rudder/3.1
- 02:21 Revision 527427a1 (rudder): Merge branch 'bug_10133/included_time_ended_in_status_dropdown_pr' into branches/rudder/3.1
- 02:19 Revision 54599b12 (rudder): Merge branch 'branches/rudder/4.1'
- 02:19 Revision c70374d1 (rudder): Merge branch 'branches/rudder/4.1'
- 02:18 Revision 81af20e5 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 02:18 Revision 1a1c9523 (rudder): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 02:08 Revision 5ee53d61 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 02:08 Revision df50a7cf (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 01:54 Revision b4c978b2 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 01:54 Revision c4361e99 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 01:53 User story #10157 (Pending release): Add an option to not display rule status/recent changes in directives screen
- Applied in changeset commit:rudder|0dbb5363d2c7d1708681d49b146a370ca9ee8b87.
- 01:50 Revision 692d2536 (rudder): Fixes #10157: Add an option to not display rule status/recent changes in directives screen
- 01:50 Revision 0dbb5363 (rudder): Fixes #10157: Add an option to not display rule status/recent changes in directives screen
Also available in: Atom