Activity
From 2014-12-15 to 2014-12-15
2014-12-15
- 21:16 Bug #5996: Display of legend in the dashboard is not really readable
- Sounds good but please replace "Bad" by "Poor".
- 11:06 Bug #5996: Display of legend in the dashboard is not really readable
- I think we should change the legend :
* 100% -> Perfect (100%)
* 75-100% -> Good ( > 75% )
* 50-75% -> Average (... - 10:59 Bug #5996 (Released): Display of legend in the dashboard is not really readable
- If i hover on the pies on the dashboard, i get notations that are not exactly readable (see screenshot). there should...
- 19:00 Bug #5971: Calendar in japanese
- Applied in changeset commit:5e1a8264b1010ab40891c4ff582161797c967986.
- 19:00 Bug #5971 (Pending release): Calendar in japanese
- Applied in changeset commit:cef8537f972881a6adc787e6150fc4b82623ecb5.
- 18:20 Bug #5971 (Pending technical review): Calendar in japanese
- https://github.com/Normation/rudder/pull/723
- 18:06 Bug #5971: Calendar in japanese
- This appeared in 2.11
- 19:00 Revision 077e514b (rudder): Merge pull request #723 from ncharles/bug_5971/dev/calendar_in_japanese
- Fixes #5971: set the local of the calendar to english by default
- 19:00 Revision 5e1a8264 (rudder): Merge pull request #723 from ncharles/bug_5971/dev/calendar_in_japanese
- Fixes #5971: set the local of the calendar to english by default
- 18:19 Revision 5e33e639 (rudder): Fixes #5971: set the local of the calendar to english by default
- 18:19 Revision cef8537f (rudder): Fixes #5971: set the local of the calendar to english by default
- 18:00 Bug #6006 (Released): Event log for send metrics popup is missing
- We need an event log to track metrics changes at the top level (in admin / preference page).
- 17:57 User story #6004 (Pending technical review): Add a boostrap popup for 'metrics' property
- PR here: https://github.com/Normation/rudder/pull/722
- 17:32 User story #6004 (Released): Add a boostrap popup for 'metrics' property
- Define a new 'look' for popups using bootstrap modal instead of jqueryUI onee we use.
- 17:53 Revision 1fc5ca2e (rudder): Fixes #6004: Add a popup to set 'metrics' property
- 17:53 Revision 363313c6 (rudder): Fixes #6004: Add a popup to set 'metrics' property
- 17:49 Bug #5888: Status of Rule is displayed as "N/A"
- Ok, the issue here is we display immediately the rule list after updating the directive, but we rely on data post pro...
- 17:38 Bug #6005 (Released): If a node had a date in the future, but returned to current time, the reporting will always be invalid (until it catches up with the future date)
- If i set the date of a node in the future, then restore it to current time, it will always have no report/unexepected...
- 17:30 User story #6003 (Released): Display a popup when 'metrics' property is not set
- We want people to know that they can send use anonymous metrics to help rudder development.
We want a popup to be ... - 17:26 Architecture #5298 (Released): Use JSON as datas of tables in Rudder web interface ( second edition)
- 17:26 Architecture #5298 (Pending release): Use JSON as datas of tables in Rudder web interface ( second edition)
- 17:25 Architecture #5298: Use JSON as datas of tables in Rudder web interface ( second edition)
- 17:25 Architecture #5298: Use JSON as datas of tables in Rudder web interface ( second edition)
- 17:24 User story #5299 (Released): Datas in Rudder web interface table can now be refreshed (second edition)
- 17:24 User story #5299 (Pending release): Datas in Rudder web interface table can now be refreshed (second edition)
- 17:24 User story #5299: Datas in Rudder web interface table can now be refreshed (second edition)
- 14:32 Bug #6002 (Rejected): Services management 2.0 reports unknown status when disabling a service at start
- With services management 2.0, i get a unknow report when config is repaired
Service starting parameters, with the fo... - 14:31 Bug #6001 (Released): Change request are not migrated to fileformat 6
- If change requests were created with a Rudder version before 3.0, when we try to read them with Rudder 3.0 we are get...
- 14:11 Bug #6000 (Released): Error output on Time settings at first run
- The first execution of Time Settings 3.0 technique outputs following message on Centos 6...
- 14:07 Bug #5999: Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- Applied in changeset policy-templates:commit:28214d7f3eef9c7e613d11a5a349ec5a4aa57911.
- 14:07 Bug #5999 (Pending release): Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- Applied in changeset policy-templates:commit:5dbbf1bed370d5bdd377366f1dd6bd875d16d347.
- 14:07 Bug #5999 (Pending technical review): Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- PR https://github.com/Normation/rudder-techniques/pull/615
- 12:43 Bug #5999 (Released): Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- We have reports: on rudder_stdlib_core.st, as it is where we define the rudder_common_report, but the check_technique...
- 14:07 Revision 28214d7f (rudder-techniques): Merge pull request #615 from peckpeck/bug_5999/tests_on_rudder_techniques_are_wrongly_failing_on_rudder_stdlib_core_st
- Fixes #5999: Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- 14:05 Revision 5dbbf1be (rudder-techniques): Fixes #5999: Tests on rudder-techniques are (wrongly) failing on rudder_stdlib_core.st
- 12:51 Revision ccc385b2 (rudder-techniques): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 12:50 Revision cfb681d3 (rudder-techniques): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 12:31 Bug #5998: On a node not yet accepted on the server, inventories are not generated in the correct location - in ${ }
- Applied in changeset policy-templates:commit:915a5102c99c559a21f8f141fdcf251340591910.
- 12:31 Bug #5998 (Pending release): On a node not yet accepted on the server, inventories are not generated in the correct location - in ${ }
- Applied in changeset policy-templates:commit:7371293f381bf4afe52926db276d2dd9895fcff1.
- 12:20 Bug #5998 (Pending technical review): On a node not yet accepted on the server, inventories are not generated in the correct location - in ${ }
- https://github.com/Normation/rudder-techniques/pull/614
- 12:12 Bug #5998: On a node not yet accepted on the server, inventories are not generated in the correct location - in ${ }
- Due to a typo, inventories are generated in folder ${/var/rudder/tmp/inventory/sys-uuid.ocs}, which is obviously wrong
- 12:11 Bug #5998 (Released): On a node not yet accepted on the server, inventories are not generated in the correct location - in ${ }
- 12:31 Revision 915a5102 (rudder-techniques): Merge pull request #614 from ncharles/bug_5998/dev/wrong_path_for_inventories
- Fixes #5998: don't overexpand path for local inventory generation in ini...
- 12:19 Revision 7371293f (rudder-techniques): Fixes #5998: don't overexpand path for local inventory generation in initial promises
- 12:17 Bug #5997: Initial promises are calling undefined body u_bootstart
- Applied in changeset policy-templates:commit:598291ee523d520b01eb144a7f0c38ce9868a5da.
- 12:17 Bug #5997 (Pending release): Initial promises are calling undefined body u_bootstart
- Applied in changeset policy-templates:commit:1844ea95e2e1e4b7996eeac5c55c9f79534dc85f.
- 12:09 Bug #5997 (Pending technical review): Initial promises are calling undefined body u_bootstart
- https://github.com/Normation/rudder-techniques/pull/613
- 12:04 Bug #5997 (Released): Initial promises are calling undefined body u_bootstart
- In the initial promises, we call a never defined body called u_bootstart, causing the agent to fail to run, and so to...
- 12:17 Revision 598291ee (rudder-techniques): Merge pull request #613 from ncharles/bug_5997/dev/add_u_bootstart
- Fixes #5997: add missing body u_bootstart into initial promises
- 12:08 Revision 1844ea95 (rudder-techniques): Fixes #5997: add missing body u_bootstart into initial promises
- 11:57 Bug #5954: Don't check for e2s binairies and template presence in the tools folder
- The check of the tools folder was introduced on 2.11, so it is normal that this ticket targets 2.11
- 11:51 Bug #5954: Don't check for e2s binairies and template presence in the tools folder
- Is it a problem that this was fixed in 2.11, and the releated issue (#5762) was fixed in 2.10 ?
- 11:28 Bug #5866 (Pending technical review): ncf API hooks don't always fail on errors
- New PR https://github.com/Normation/rudder-packages/pull/567
- 11:25 Bug #5334: The archiving logic of execution reports needs to be adapted for "error only" report mode
- I'm not sure anymore of the the rationnal for that, because:
- we have at least one report batch sent by day (inv... - 09:30 Revision e0252791 (rudder): Merge branch 'branches/rudder/3.0'
- 09:30 Revision 81a941aa (rudder): Merge branch 'branches/rudder/3.0'
- 09:29 Revision 7c0ca0c1 (rudder): Merge branch 'branches/rudder/3.0'
- 09:29 Revision 7c0ca0c1 (ldap-inventory): Merge branch 'branches/rudder/3.0'
Also available in: Atom