Activity
From 2016-10-18 to 2016-10-18
2016-10-18
- 23:27 Bug #9444: When accepting 100 nodes, I randomly get multiple policy generation
- ok, some more details:
After accepting one node, and hitting once update, I get 3 opened node configuration for all ... - 23:10 Bug #9444: When accepting 100 nodes, I randomly get multiple policy generation
- interestingly, hitting "update" right after accepting a node triggers a full generation, and increase the number of o...
- 23:07 Bug #9444: When accepting 100 nodes, I randomly get multiple policy generation
- ok, accepting one node doubled the number of opened node configuration
Detail debugs are:... - 22:56 Bug #9444: When accepting 100 nodes, I randomly get multiple policy generation
- clear cache restore a sane number of opened nodeconfiguration
- 22:56 Bug #9444 (Rejected): When accepting 100 nodes, I randomly get multiple policy generation
- I accepted 100 nodes, and as a result, I had:...
- 23:01 Bug #9445 (Released): If we filter event logs with only a start or end date, we get a super ugly error
- If I set only a start or end date for filtering event log, the error is awful:...
- 22:37 Bug #9443 (Released): When clicking on the "edit group" on the Rule details, we don't get redirected to the said group
- If I click on the pen to edit the group on the rule details, i arrive on the groups page, but the details of the grou...
- 22:18 User story #9229: Document Postgresql 9.2 recommandation
- https://github.com/Normation/rudder-doc/pull/243
- 22:13 Bug #9359 (Pending release): Agent capabilities should be per agent, and not per node
- Applied in changeset commit:rudder-techniques|d0a9cc987316354750a574f0001b387bba10ddc1.
- 22:13 Revision 63f6e61b (rudder-techniques): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 22:13 Revision 0c241148 (rudder-techniques): Merge branch 'bug_9359/agent_capabilities_should_be_per_agent_and_not_per_node_pr' into branches/rudder/3.2
- 19:21 Bug #9424 (Pending release): Scrollbar appears on technique editor page
- Applied in changeset commit:rudder|84855177bc68a33a2ac220ec0a3f9ab731bd2986.
- 17:37 Bug #9424 (In progress): Scrollbar appears on technique editor page
- 15:20 Bug #9424 (Released): Scrollbar appears on technique editor page
- When on the technique editor page,, the content is a bit too high for the page, and a scollbar appears.
- 19:21 Revision b9ad9536 (rudder): Merge branch 'bug_9424/scrollbar_appears_on_technique_editor_page_pr' into branches/rudder/4.0
- 19:21 Revision bee4ada1 (rudder): Merge branch 'bug_9424/scrollbar_appears_on_technique_editor_page_pr' into branches/rudder/4.0
- 19:20 Bug #9437 (Pending release): Unclear popup on compliance bar
- Applied in changeset commit:rudder|c37d234731e15d0b7471ad47a7763e89b10e3485.
- 17:16 Bug #9437 (Pending technical review): Unclear popup on compliance bar
- PR https://github.com/Normation/rudder/pull/1296
- 17:02 Bug #9437 (In progress): Unclear popup on compliance bar
- 16:51 Bug #9437 (Released): Unclear popup on compliance bar
- see screenshot, it is not easily readable.
- 19:20 Revision 7839c1cd (rudder): Merge branch 'bug_9437/unclear_popup_on_compliance_bar_pr' into branches/rudder/4.0
- 19:20 Revision 88cffdde (rudder): Merge branch 'bug_9437/unclear_popup_on_compliance_bar_pr' into branches/rudder/4.0
- 19:19 Bug #9428 (Pending release): Popups should be closable/navigable with the keybord
- Applied in changeset commit:rudder|528e72f55acb404abe90ede468eb7a0b6cdfc584.
- 17:35 Bug #9428 (Pending technical review): Popups should be closable/navigable with the keybord
- PR https://github.com/Normation/rudder/pull/1297
- 15:36 Bug #9428 (Released): Popups should be closable/navigable with the keybord
- Some popups are not usable with the keyboard (like the popup after saving a directive), which is an inconvenient regr...
- 19:19 Revision ed615bda (rudder): Merge branch 'bug_9428/popups_should_be_closable_navigable_with_the_keybord_pr' into branches/rudder/4.0
- 19:19 Revision 8171ff9d (rudder): Merge branch 'bug_9428/popups_should_be_closable_navigable_with_the_keybord_pr' into branches/rudder/4.0
- 19:18 Bug #9427 (Pending release): Error message is displayed while loading API accounts table
- Applied in changeset commit:rudder|81675817c1046a6a76360094d98b3ff9d3998aa5.
- 18:02 Bug #9427 (Pending technical review): Error message is displayed while loading API accounts table
- PR https://github.com/Normation/rudder/pull/1300
- 17:54 Bug #9427 (In progress): Error message is displayed while loading API accounts table
- 15:32 Bug #9427 (Released): Error message is displayed while loading API accounts table
- See attached screenshot, the message disappears when the table is loaded.
- 19:18 Revision 76c06963 (rudder): Merge branch 'bug_9427/error_message_is_displayed_while_loading_api_accounts_table_pr' into branches/rudder/4.0
- 19:18 Revision 2a2e3362 (rudder): Merge branch 'bug_9427/error_message_is_displayed_while_loading_api_accounts_table_pr' into branches/rudder/4.0
- 19:16 Bug #9425 (Pending release): When a component value is on mixed mode, the message goes out of the compliance table
- Applied in changeset commit:rudder|e0d3009f8a70066ede3bf45135bb9558dee58975.
- 16:42 Bug #9425 (Pending technical review): When a component value is on mixed mode, the message goes out of the compliance table
- PR https://github.com/Normation/rudder/pull/1293
- 15:48 Bug #9425 (In progress): When a component value is on mixed mode, the message goes out of the compliance table
- 15:20 Bug #9425 (Released): When a component value is on mixed mode, the message goes out of the compliance table
- When we go to see the details of a component in a node (or rule) compliance tree, and the componenent is reporting a ...
- 19:16 Revision 3113a455 (rudder): Merge branch 'bug_9425/when_a_component_value_is_on_mixed_mode_the_message_goes_out_of_the_compliance_table_pr' into branches/rudder/4.0
- 19:16 Revision 0466a114 (rudder): Merge branch 'bug_9425/when_a_component_value_is_on_mixed_mode_the_message_goes_out_of_the_compliance_table_pr' into branches/rudder/4.0
- 19:14 Bug #9271 (Pending technical review): Selected directive in directive tree doesn't remain highlighed
- PR https://github.com/Normation/rudder/pull/1301
- 19:09 Architecture #9440 (Rejected): Directives are not correctly grouped in nodeconfiguration table
- The configuration json contains:...
- 18:47 Revision 64e2d531 (rudder): Fixes #9424: Scrollbar appears on technique editor page
- 18:47 Revision 84855177 (rudder): Fixes #9424: Scrollbar appears on technique editor page
- 18:41 User story #9269: Add IPV6 support in rudder-init
- PR https://github.com/Normation/rudder-packages/pull/1115
- 18:41 Revision be98c596 (rudder-packages): Fixes #9269: Add IPV6 support in rudder-init
- 18:36 User story #9372 (In progress): Repaire and improve Change Request page
- 11:52 User story #9372: Repaire and improve Change Request page
- Like in #9341, the solution may be to add bootstrap.
- 18:15 User story #9439 (Pending technical review): Use $releasever in upgrade section for RHEL
- PR https://github.com/Normation/rudder-doc/pull/242
- 18:09 User story #9439 (In progress): Use $releasever in upgrade section for RHEL
- 18:07 User story #9439 (Released): Use $releasever in upgrade section for RHEL
- To replace the current RHEL_7 hardcoded version.
- 18:15 Revision dfd55a12 (rudder-doc): Fixes #9439: Use $releasever in upgrade section for RHEL
- 18:03 Revision 67111478 (rudder-doc): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 18:02 Revision d94cf175 (rudder): Fixes #9427: Error message is displayed while loading API accounts table
- 18:02 Revision 81675817 (rudder): Fixes #9427: Error message is displayed while loading API accounts table
- 18:00 Revision 94298ef8 (rudder-doc): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 17:58 User story #9422 (Pending release): Update documentation to have version independant repo
- Applied in changeset commit:rudder-doc|0a91cd37719b94707559a06d4c2b4f1bb49efca7.
- 15:15 User story #9422 (Pending technical review): Update documentation to have version independant repo
- PR https://github.com/Normation/rudder-doc/pull/241
- 15:13 User story #9422 (In progress): Update documentation to have version independant repo
- 15:12 User story #9422 (Released): Update documentation to have version independant repo
- The documentation uses hardcoded (but autodetected) distribution versions.
It would be much better for the use tha... - 17:57 Bug #9323: Compliance display when hoverving over the compliance bar is too precise
- It looks like the backend returns values with a correct precision and the JS makes questionable rounding.
- 17:39 Bug #9438 (Pending technical review): The link in the Rudder interface should not use french Normation website link
- PR https://github.com/Normation/rudder/pull/1298
- 17:38 Bug #9438 (In progress): The link in the Rudder interface should not use french Normation website link
- 17:37 Bug #9438 (Released): The link in the Rudder interface should not use french Normation website link
- But instead use the root url with auto-detection of the language
- 17:38 Revision 98e8b61d (rudder): Fixes #9438: The link in the Rudder interface should not use french Normation website link
- 17:38 Revision feea99ab (rudder): Fixes #9438: The link in the Rudder interface should not use french Normation website link
- 17:35 Revision 188104e1 (rudder): Fixes #9428: Popups should be closable/navigable with the keybord
- 17:35 Revision 528e72f5 (rudder): Fixes #9428: Popups should be closable/navigable with the keybord
- 17:33 Revision 0a91cd37 (rudder-doc): Fixes #9422: Update documentation to have version independant repo
- 17:24 User story #9421 (In progress): Add the Rudder abort handler to ncf.conf
- 15:11 User story #9421 (Released): Add the Rudder abort handler to ncf.conf
- We need to add our handler like the logger.
- 17:18 User story #9351: Create a dedicated abort report when enforce is used in place of audit
- In #9420 we added:
rudder_common_report("Common", "log_info", "&TRACKINGKEY&", "Abort run", "${reason}", "${messag... - 17:17 Architecture #9417 (In progress): Correct test on expected reports and clean code
- 13:20 Architecture #9417 (Released): Correct test on expected reports and clean code
- There was a lot of tests that were disabled during #9315 because the structure of expected reports changed so much. N...
- 17:15 Revision 8c4086cf (rudder): Fixes #9437: Unclear popup on compliance bar
- 17:15 Revision c37d2347 (rudder): Fixes #9437: Unclear popup on compliance bar
- 17:09 Bug #9311 (Pending release): On Search nodes page, if I click on "Include Rudder server components" checkbox, I get a JS error
- Applied in changeset commit:rudder|520ba1468e500e60e14a2e128c3c03143f119395.
- 17:04 Bug #9311 (Pending technical review): On Search nodes page, if I click on "Include Rudder server components" checkbox, I get a JS error
- PR https://github.com/Normation/rudder/pull/1295
- 15:20 Bug #9311 (In progress): On Search nodes page, if I click on "Include Rudder server components" checkbox, I get a JS error
- 17:09 Revision b4731383 (rudder): Merge branch 'bug_9311/on_search_nodes_page_if_i_click_on_include_rudder_server_components_checkbox_i_get_a_js_error_pr' into branches/rudder/4.0
- 17:09 Revision b90f4dd1 (rudder): Merge branch 'bug_9311/on_search_nodes_page_if_i_click_on_include_rudder_server_components_checkbox_i_get_a_js_error_pr' into branches/rudder/4.0
- 17:09 User story #9410 (Pending release): Add a new abort parameter in ncf.conf
- Applied in changeset commit:c1e41a5b14c56d59eec8cfb46046f30c612c52a0.
- 12:17 User story #9410 (Pending technical review): Add a new abort parameter in ncf.conf
- PR https://github.com/Normation/ncf/pull/478
- 11:56 User story #9410 (In progress): Add a new abort parameter in ncf.conf
- 11:56 User story #9410 (Released): Add a new abort parameter in ncf.conf
- We need a plugin system for aborting.
- 17:09 Revision eac59a07 (ncf): Merge branch 'ust_9410/add_a_new_abort_parameter_in_ncf_conf_pr'
- 17:06 User story #9435 (Pending release): Replace the old icon by the new one
- Applied in changeset commit:rudder|cb6914c02a2dbb54e17aa258bd512b3c9b781e33.
- 17:01 User story #9435 (Pending technical review): Replace the old icon by the new one
- PR https://github.com/Normation/rudder/pull/1294
- 16:46 User story #9435 (In progress): Replace the old icon by the new one
- 16:46 User story #9435 (Released): Replace the old icon by the new one
!old-icon.png!- 17:03 Revision 432c62f8 (rudder): Fixes #9311: On Search nodes page, if I click on "Include Rudder server components" checkbox, I get a JS error
- 17:03 Revision 520ba146 (rudder): Fixes #9311: On Search nodes page, if I click on "Include Rudder server components" checkbox, I get a JS error
- 17:01 Revision 0e9db4d2 (rudder): Fixes #9435: Replace the old icon by the new one
- 17:01 Revision cb6914c0 (rudder): Fixes #9435: Replace the old icon by the new one
- 16:51 User story #9420 (Pending release): Define the _abort_rudder bundle that will be called in ncf
- Applied in changeset commit:rudder-techniques|e915581b5cbe837894eea9bb6aafbba633fbe3ed.
- 15:06 User story #9420 (Pending technical review): Define the _abort_rudder bundle that will be called in ncf
- PR https://github.com/Normation/rudder-techniques/pull/1060
- 14:59 User story #9420 (In progress): Define the _abort_rudder bundle that will be called in ncf
- 14:48 User story #9420 (Released): Define the _abort_rudder bundle that will be called in ncf
- We need an _abort_rudder handler that makes a log_info report to the webapp.
- 16:49 Bug #9436 (Released): Error message when failing to accept a new node is hard to find
- When we have error when trying to accept new node, the error message is not really readable (see screenshot)
It shou... - 16:49 Bug #9431 (Pending release): http* methods should allow enmpty headers field
- Applied in changeset commit:435643407064083b3ca606357951c8fd7e696c9e.
- 16:02 Bug #9431 (Pending technical review): http* methods should allow enmpty headers field
- PR https://github.com/Normation/ncf/pull/479
- 16:01 Bug #9431 (In progress): http* methods should allow enmpty headers field
- 16:00 Bug #9431 (Released): http* methods should allow enmpty headers field
- We need to add the right constraint.
- 16:48 Revision 8092a57d (ncf): Merge branch 'v0.x'
- 16:42 Revision 7c528d62 (rudder): Fixes #9425: When a component value is on mixed mode, the message goes out of the compliance table
- 16:42 Revision e0d3009f (rudder): Fixes #9425: When a component value is on mixed mode, the message goes out of the compliance table
- 16:21 Bug #9433 (Released): Incorrect inventory on Rudder server
- ...
- 16:11 Bug #9432 (Released): No Rudder report for http_request_content_headers
- ...
- 16:02 Revision 43564340 (ncf): Fixes #9431: http* methods should allow enmpty headers field
- 15:46 Bug #9430 (Rejected): Strange reporting in audit mode for file enforce content
- ...
- 15:41 Bug #9429 (Released): An horizontal scrollbar appears on the dashboard when hovering over the right graph
- See attached screenshot, the messages goes out of the screen.
- 15:27 Bug #9426 (Released): Inconsistent message style in settings page
- The style of the message for reload technique/group is different, see attached screenshot.
- 15:26 Bug #9297 (Pending release): When generation failed due to mixed mode on one technique, error says "plop"
- Applied in changeset commit:rudder|d64c486886d0382fd16ee9a557dc847fc5bf1e5f.
- 13:52 Bug #9297 (Pending technical review): When generation failed due to mixed mode on one technique, error says "plop"
- PR https://github.com/Normation/rudder/pull/1289
- 13:21 Bug #9297 (In progress): When generation failed due to mixed mode on one technique, error says "plop"
- 15:26 Revision 321b4381 (rudder): Merge branch 'bug_9297/when_generation_failed_due_to_mixed_mode_on_one_technique_error_says_plop_pr' into branches/rudder/4.0
- 15:26 Revision eb3025a4 (rudder): Merge branch 'bug_9297/when_generation_failed_due_to_mixed_mode_on_one_technique_error_says_plop_pr' into branches/rudder/4.0
- 15:18 Bug #9339 (Rejected): When I click on the date picker on the Node Detail/Technical log, I get 404 errors
- fixed by #9251
- 15:17 Bug #9399 (Rejected): Deleting a node keep us on the node details page
- 02:20 Bug #9399 (Rejected): Deleting a node keep us on the node details page
- When we delete a node and confirm, we remains on the node page, which is a little strange (because the node is delete...
- 15:17 Bug #9340 (Rejected): Display of harware tab, in "Accept new node" page is broken
- 15:16 Bug #9338 (Rejected): When I arrive on the node details page, the URL is badly rewriten
- Fixed by #9251
- 15:15 Bug #9286 (Rejected): On the node detail if we hit F5 or try to reload page, we arrive on the search node page
- Fixed by #9251
- 15:09 User story #9261 (Pending release): "change only" reporting mode is not accurate for "audit" policy mode
- Applied in changeset commit:rudder|ea3c9d06fe46d1261dc53cf3e414a379ef01757b.
- 15:04 User story #9261 (Pending technical review): "change only" reporting mode is not accurate for "audit" policy mode
- PR https://github.com/Normation/rudder/pull/1292
- 14:54 User story #9261 (In progress): "change only" reporting mode is not accurate for "audit" policy mode
- 15:08 Revision ada29f59 (rudder): Merge branch 'ust_9261/change_only_reporting_mode_is_not_accurate_for_audit_policy_mode_pr' into branches/rudder/4.0
- 15:08 Revision fa0bc545 (rudder): Merge branch 'ust_9261/change_only_reporting_mode_is_not_accurate_for_audit_policy_mode_pr' into branches/rudder/4.0
- 15:08 Bug #9251 (Pending release): Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
- Applied in changeset commit:rudder|977dca54dc5a16344012a36f7e9aa4fa20daea8c.
- 15:00 Bug #9251 (Pending technical review): Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
- PR https://github.com/Normation/rudder/pull/1291
- 11:08 Bug #9251 (In progress): Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
- 15:08 Revision 50c531fe (rudder): Merge branch 'bug_9251/infamous_server_cannot_be_contacted_at_this_time_when_trying_to_access_node_details_of_a_deleted_node_pr' into branches/rudder/4.0
- 15:08 Revision 3b53a4ff (rudder): Merge branch 'bug_9251/infamous_server_cannot_be_contacted_at_this_time_when_trying_to_access_node_details_of_a_deleted_node_pr' into branches/rudder/4.0
- 15:07 Bug #9341 (Pending release): Wrong alignement of fields on group page
- Applied in changeset commit:rudder|42e1d21be74e1c1fe3bb690207835c1332e85969.
- 14:39 Bug #9341 (Pending technical review): Wrong alignement of fields on group page
- PR https://github.com/Normation/rudder/pull/1290
- 11:17 Bug #9341 (In progress): Wrong alignement of fields on group page
- 10:37 Bug #9341: Wrong alignement of fields on group page
- The simplest solution seems to be to use bootstrap for the form, which is utterly broken.
- 15:07 Revision fb929f46 (rudder): Merge branch 'bug_9341/wrong_alignement_of_fields_on_group_page_pr' into branches/rudder/4.0
- 15:07 Revision bf217c84 (rudder): Merge branch 'bug_9341/wrong_alignement_of_fields_on_group_page_pr' into branches/rudder/4.0
- 15:05 Revision e915581b (rudder-techniques): Fixes #9420: Define the _abort_rudder bundle that will be called in ncf
- 15:04 Revision 14a3b4c8 (rudder): Fixes #9261: "change only" reporting mode is not accurate for "audit" policy mode
- 15:04 Revision ea3c9d06 (rudder): Fixes #9261: "change only" reporting mode is not accurate for "audit" policy mode
- 15:04 Bug #9400 (Pending release): On accept node page, [Accept] button should be on right. Or green. Or both.
- Applied in changeset commit:rudder|ce91c0f16ea23abcf2eebb6f2619eceac2bbb50e.
- 11:15 Bug #9400 (Pending technical review): On accept node page, [Accept] button should be on right. Or green. Or both.
- PR https://github.com/Normation/rudder/pull/1286
- 11:02 Bug #9400 (In progress): On accept node page, [Accept] button should be on right. Or green. Or both.
- 02:28 Bug #9400 (Released): On accept node page, [Accept] button should be on right. Or green. Or both.
- When we go to the "accept new nodes" page, the [Accept] button is complettly on left, almost invisible (because most ...
- 15:04 Revision bfb71e93 (rudder): Merge branch 'bug_9400/on_accept_node_page_accept_button_should_be_on_right_or_green_or_both_pr' into branches/rudder/4.0
- 15:04 Revision 7702493f (rudder): Merge branch 'bug_9400/on_accept_node_page_accept_button_should_be_on_right_or_green_or_both_pr' into branches/rudder/4.0
- 15:01 Bug #9233 (New): Error during upgrade from 3.2 to 4.0
- actually, i can reproduce it:...
- 14:44 Bug #9233 (Rejected): Error during upgrade from 3.2 to 4.0
- cannot reproduce on centos 6 either
- 14:37 Bug #9233: Error during upgrade from 3.2 to 4.0
- could not reproduce (on centos7)
- 15:00 Revision 70aa996e (rudder): Fixes #9251: Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
- 15:00 Revision 977dca54 (rudder): Fixes #9251: Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
- 14:58 Bug #9419 (Rejected): Error on pcre on centos6
- Wrong package installed, centos7 on centos6
sorry - 14:54 Bug #9419: Error on pcre on centos6
- ...
- 14:46 Bug #9419 (Rejected): Error on pcre on centos6
- While upgrading rudder-agent from 3.1 to 4.0 on centos6, i got the following errors:...
- 14:53 Revision aaff91c7 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 14:53 Revision 251bb7c7 (rudder): Merge branch 'branches/rudder/3.2' into branches/rudder/4.0
- 14:50 Revision 13657983 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 14:50 Revision f6eda5c3 (rudder): Merge branch 'branches/rudder/3.1' into branches/rudder/3.2
- 14:50 Bug #9402 (Pending release): Node properties update doesn't invalidate node configuration hash
- Applied in changeset commit:rudder|a7df590f3c2c06853e812184f8bf213995ddf721.
- 09:51 Bug #9402 (Pending technical review): Node properties update doesn't invalidate node configuration hash
- PR https://github.com/Normation/rudder/pull/1284
- 09:46 Bug #9402 (Released): Node properties update doesn't invalidate node configuration hash
- If node properties are updated, and the properties are not used in a directive, then the node configuration hash is n...
- 14:50 Revision 43ad5a58 (rudder): Merge pull request #1284 from fanf/bug_9402/node_properties_update_doesn_t_invalidate_node_configuration_hash
- Fixes #9402: Node properties update doesn't invalidate node configuration hash
- 14:50 Revision e2034ea7 (rudder): Merge pull request #1284 from fanf/bug_9402/node_properties_update_doesn_t_invalidate_node_configuration_hash
- Fixes #9402: Node properties update doesn't invalidate node configuration hash
- 14:49 Bug #9397 (Pending release): logback.xml doesn't contains most entries in 4.0
- Applied in changeset commit:rudder|645706b9551235bf4f8fa24b84ae07a0897f7f13.
- 14:49 Revision ccd78cb0 (rudder): Merge branch 'bug_9397/logback_xml_doesn_t_contains_most_entries_in_4_0_pr' into branches/rudder/4.0
- 14:49 Revision ba139483 (rudder): Merge branch 'bug_9397/logback_xml_doesn_t_contains_most_entries_in_4_0_pr' into branches/rudder/4.0
- 14:47 Bug #9295 (Pending release): The old bundlesequence system variable contains contains Bundle(...)
- Applied in changeset commit:rudder|dc58889e56ef2d1da6a555864926bbe6799ef075.
- 13:10 Bug #9295 (Pending technical review): The old bundlesequence system variable contains contains Bundle(...)
- PR https://github.com/Normation/rudder/pull/1288
- 14:42 Revision c1e41a5b (ncf): Fixes #9410: Add a new abort parameter in ncf.conf
- 14:41 User story #9418 (Released): Parse Timezone information in inventory
- Now that we have a timezone info in the inventory, we need to parse them and add them in NodeInventory object to be a...
- 14:39 Revision afd5b989 (rudder): Fixes #9341: Wrong alignement of fields on group page
- 14:39 Revision 42e1d21b (rudder): Fixes #9341: Wrong alignement of fields on group page
- 13:52 Revision 69a320a2 (rudder): Fixes #9297: When generation failed due to mixed mode on one technique, error says "plop"
- 13:52 Revision d64c4868 (rudder): Fixes #9297: When generation failed due to mixed mode on one technique, error says "plop"
- 13:16 Bug #9332 (Rejected): If we are in audit mode, and agent does not support audit, the web interface shows "No answer" for this node
- It was more a problem on the node run, not in the compliance part. It was corrected along with the work on #9092
- 13:14 Bug #9416: Transient error during upgrade from 3.1 to 4.0
- We should never generate new promises while distributing old ncf - rudder agent update should be part of the upgrade ...
- 13:11 Bug #9416 (Rejected): Transient error during upgrade from 3.1 to 4.0
- When upgrading from 3.1 to 4.0, we have a several minute long "no reports" on the web interface
Reason is promises a... - 13:10 Revision 3a77d3c2 (rudder): Fixes #9295: The old bundlesequence system variable contains contains Bundle(...)
- 13:10 Revision dc58889e (rudder): Fixes #9295: The old bundlesequence system variable contains contains Bundle(...)
- 13:04 Bug #9401 (Pending release): Deleting a node should close its expected configuration
- Applied in changeset commit:rudder|1bf3d6f780ba2eace330ddff498aa48b5ffaec66.
- 12:58 Bug #9401 (Pending technical review): Deleting a node should close its expected configuration
- PR https://github.com/Normation/rudder/pull/1287
- 12:31 Bug #9401 (In progress): Deleting a node should close its expected configuration
- 02:31 Bug #9401 (Released): Deleting a node should close its expected configuration
- When a node is deleted from rudder, we should close its expected configuration.
(in my case, I had deleted and reac... - 12:58 Revision cdacae9b (rudder): Fixes #9401: Deleting a node should close its expected configuration
- 12:58 Revision 1bf3d6f7 (rudder): Fixes #9401: Deleting a node should close its expected configuration
- 12:55 Bug #9415 (Released): Nodes have several open nodeconfigurations
- On my test machine, I get to the situation where nodes have several opened expected node configurations: ...
- 12:48 Bug #9414 (Pending release): AIX doesn't build on 4.0
- Applied in changeset commit:rudder-packages|f1c52e5b571bc193c471995f75b5bc0a08ce279b.
- 12:47 Bug #9414 (Pending technical review): AIX doesn't build on 4.0
- PR https://github.com/Normation/rudder-packages/pull/1114
- 12:47 Bug #9414 (In progress): AIX doesn't build on 4.0
- 12:47 Bug #9414 (Released): AIX doesn't build on 4.0
- There was a bug in the resolution of #9405
- 12:47 Revision f1c52e5b (rudder-packages): Fixes #9414: AIX doesn't build on 4.0
- 12:46 Bug #9413 (Rejected): AIX doesn't build on 4.0
- There was a bug in the resolution of #9405
- 12:41 Bug #9412 (Released): Unexpected dependency on XML::TreePP on rudder-technique on Centos7
- Trying to update rudder on Centos7, I have the following error message:...
- 12:28 Bug #9331 (Rejected): Compliance report in audit mode is broken for system techniques
- It was corrected along with #9315
- 12:22 Architecture #8005: API directives - one extra nesting level?
- Hum.
For an explanation before even trying to know if it is ok: it is due to the structure of directive parameter... - 12:11 User story #8125 (Rejected): Make eventlog migration faster (parallilised)
- Actually, we most likelly don't care, because we most likelly won't migrate event log any further (cf #9202)
- 12:06 Bug #8528 (Rejected): Non existing files in AIX build
- Duplicates #9373
- 12:02 Architecture #8964 (Rejected): Update documentation to explaine Java8 requirment in Rudder 4.0
- 12:00 Bug #9333 (Pending release): If we change the global policy mode, promises are not generated if we click on "update policies"
- Applied in changeset commit:rudder|16b718d88fc46f8c5a7470fd64048f33ae50e57d.
- 03:32 Bug #9333 (Pending technical review): If we change the global policy mode, promises are not generated if we click on "update policies"
- PR https://github.com/Normation/rudder/pull/1283
- 11:57 Architecture #9411 (Rejected): Remove duplicated rudder_common_report
- rudder_common_report has been duplicated in logger_rudder because we had to support rudder 2.11 which didn't have tho...
- 11:37 User story #9409 (In progress): Add a special log when audit mode is used but not supported
- 11:37 User story #9409 (Rejected): Add a special log when audit mode is used but not supported
- We need a special report for the webapp.
- 11:35 Revision 66adbda7 (rudder): Fixes #9333: If we change the global policy mode, promises are not generated if we click on "update policies"
- 11:35 Revision 16b718d8 (rudder): Fixes #9333: If we change the global policy mode, promises are not generated if we click on "update policies"
- 11:34 User story #9408 (Pending release): Update list of supported OSes in the manual
- Applied in changeset commit:rudder-doc|261a16d4b08a7c85ca2106f4859e6354ab8a904f.
- 11:20 User story #9408 (Pending technical review): Update list of supported OSes in the manual
- PR https://github.com/Normation/rudder-doc/pull/240
- 11:15 User story #9408 (In progress): Update list of supported OSes in the manual
- 11:14 User story #9408 (Released): Update list of supported OSes in the manual
- We drop Ubuntu 12.04 support in 4.0.
- 11:23 Revision 261a16d4 (rudder-doc): Fixes #9408: Update list of supported OSes in the manual
- 11:15 Revision a087d094 (rudder): Fixes #9400: On accept node page, [Accept] button should be on right. Or green. Or both.
- 11:15 Revision ce91c0f1 (rudder): Fixes #9400: On accept node page, [Accept] button should be on right. Or green. Or both.
- 11:14 Bug #9407 (Released): We should not hide exceptions in logs
- Today, we are hiding exception stack in Rudder with the logback.xml config (the Ex{0} part):
</pre>
<Patt... - 11:13 User story #9048: Add a test for action bodies that do not contain a test on dry-run classes
- I guess the best way to do this is to use cf-promises -p json + jq '.bodies' and grep dry_run.
- 11:12 Bug #9342 (Pending release): Error when trying to create a new Parameter
- Applied in changeset commit:rudder|b7f18d3ef9da6c98644fbaa947d9a1ec870e1998.
- 11:02 Bug #9342 (Pending technical review): Error when trying to create a new Parameter
- PR https://github.com/Normation/rudder/pull/1285
- 10:54 Bug #9342 (In progress): Error when trying to create a new Parameter
- 11:12 Bug #9405 (Pending release): AIX doesn't build on 4.0
- Applied in changeset commit:rudder-packages|f13ab9deae352dea238e3944b114b4276396d0b9.
- 11:09 Bug #9405 (Pending technical review): AIX doesn't build on 4.0
- PR https://github.com/Normation/rudder-packages/pull/1113
- 11:07 Bug #9405 (In progress): AIX doesn't build on 4.0
- 11:02 Bug #9405 (Released): AIX doesn't build on 4.0
- 11:09 Revision f13ab9de (rudder-packages): Fixes #9405: AIX doesn't build on 4.0
- 11:06 Bug #9406 (Released): Missing logger information for quicksearch in logback.xml
- When we added quicksearch, we added specific debug messages. They can't be discovered by a user, so logback.xml shoul...
- 11:02 Revision 8caaf185 (rudder): Fixes #9342: Error when trying to create a new Parameter
- 11:02 Revision b7f18d3e (rudder): Fixes #9342: Error when trying to create a new Parameter
- 10:51 User story #1808 (Pending release): Add an Audit mode to Rudder: only check properties, no modification on nodes
- 10:50 User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
- 10:50 User story #1808 (Pending technical review): Add an Audit mode to Rudder: only check properties, no modification on nodes
- 10:39 Bug #9404 (Released): The "Search Anything" in the search bar is not readable
- The text is in gray on orange and not very readable.
- 10:30 Bug #9403 (Rejected): Doc API remote run
- These is no documentation for the new API "remote run".
- 09:51 Revision fac5d2a7 (rudder): Fixes #9402: Node properties update doesn't invalidate node configuration hash
- 09:51 Revision a7df590f (rudder): Fixes #9402: Node properties update doesn't invalidate node configuration hash
- 09:47 User story #9354 (In progress): Add a jumbotron next to Directives list
- 09:13 Bug #9398 (Rejected): New global parameter are not displayed in the table
- Rejected as duplicate
- 02:18 Bug #9398 (Rejected): New global parameter are not displayed in the table
- When we are adding a new parameter and click on save, it is not displayed on the list of global parameters (but appea...
- 09:12 Revision c7e0ca9a (rudder): Fixes #9397: logback.xml doesn't contains most entries in 4.0
- 09:12 Revision 645706b9 (rudder): Fixes #9397: logback.xml doesn't contains most entries in 4.0
Also available in: Atom