Activity
From 2013-10-18 to 2013-10-18
2013-10-18
- 18:24 Bug #4089: A query about execution date of reports still use old parameters
- Applied in changeset commit:aebdad04d91d03feb86b5ca5ba8543dab04a41bc.
- 18:24 Bug #4089 (Pending release): A query about execution date of reports still use old parameters
- Applied in changeset commit:d41d9ee06b5de24391a940f086a319878336a18f.
- 14:46 Bug #4089: A query about execution date of reports still use old parameters
- I believe Nicolas will be better up to validate that one.
- 14:41 Bug #4089 (Pending technical review): A query about execution date of reports still use old parameters
- Pull request here: https://github.com/Normation/rudder/pull/351
- 14:26 Bug #4089 (Released): A query about execution date of reports still use old parameters
- When the function to get execution date of nodes from the database is called there is an error launched:...
- 18:24 Revision 9a27aa3b (rudder): Merge pull request #351 from VinceMacBuche/bug_4089/Fix_query
- Fixes #4089: Fix "getExecutionsByNode" query
- 18:24 Revision aebdad04 (rudder): Merge pull request #351 from VinceMacBuche/bug_4089/Fix_query
- Fixes #4089: Fix "getExecutionsByNode" query
- 18:06 Bug #4093 (Rejected): With Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message
- On Rudder 2.6 with Workflow activated, upgrading a Technique code with changes in the attributes in the same version ...
- 17:30 Bug #4092 (Rejected): On Firefox 10 the tooltips of each Directives does not disappear
- On SLES 11 SP1 with Firefox 10, each time a Directive's tooltip appear, it won't disappear until the page is reloaded
- 16:59 Bug #4091: When we migrate to 2.8, the time to catch up on all the nodes execution time is very long
- https://github.com/Normation/rudder/pull/352
- 16:59 Bug #4091 (Pending technical review): When we migrate to 2.8, the time to catch up on all the nodes execution time is very long
- With this, I go from about 40 minutes to about 1 minute to gather all the data
- 16:38 Bug #4091 (Released): When we migrate to 2.8, the time to catch up on all the nodes execution time is very long
- When upgrading to 2.8 with already data in the database, the time for the Agent Execution Service to catch up with al...
- 16:58 Revision 7a9206f9 (rudder): Fixes #4091: transform the igration script to create the data at migration time
- 16:58 Revision 4b91a6ac (rudder): Fixes #4091: transform the igration script to create the data at migration time
- 15:17 Revision b662a633 (rudder): Fixes #4089: Fix "getExecutionsByNode" query
- 15:17 Revision d41d9ee0 (rudder): Fixes #4089: Fix "getExecutionsByNode" query
- 14:42 Bug #4090 (Rejected): The migration script dbMigration-2.6-2.6-index-reports.sql could take a lots of minutes
- During an upgrade of rudder-web package (from 2.6.2 to 2.6.8 on my case) the rudder-upgrade script is launched.
From... - 12:04 Bug #4088 (Released): Error when upgrading from a Rudder server 2.3 if both policy.xml and metadata.xml were existing for the same techniques
- A long time ago, we used to have some policy.xml files instead of metadata.xml for our techniques.
This old remain... - 09:54 Bug #4025 (Pending technical review): The failsafe of the initial promises cannot update promises
- PR updated
- 09:53 Revision 20b57b83 (rudder-techniques): Fixes #4025: use correctly the uuid in the failsafe file
- 09:16 Revision 3f0130cb (rudder): Merge branch 'branches/rudder/2.8'
- 09:16 Revision e2ec2177 (rudder): Merge branch 'branches/rudder/2.8'
- 09:16 Revision d95fe016 (rudder): Merge branch 'branches/rudder/2.7' into branches/rudder/2.8
- 09:16 Revision 339d93c1 (rudder): Merge branch 'branches/rudder/2.7' into branches/rudder/2.8
Also available in: Atom