Rudder: Issueshttps://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182012-06-05T16:46:38ZIssue Tracker
Redmine Bug #2532 (Released): When deleting a Rule, the reason input is not output to the change log in githttps://issues.rudder.io/issues/25322012-06-05T16:46:38ZJonathan CLARKEjonathan.clarke@normation.com
<p>I just deleted a Rule, and entered some message like "testing", but this is what I got in the git log:</p>
<pre>
commit 290421a33ebe74d2d501fe0fc587978f6d5f546e
Author: jon.doe <email not set>
Date: Tue Jun 5 18:45:03 2012 +0200
Delete archive of configuration rule with ID 'd81f9f61-3c9c-48b1-b150-8f8e8125f528', reason: Rule deleted by user
</pre>
<p>Note: my "reason" field is set to optional (displayed but not mandatory).</p> Bug #2531 (Released): Event log column "Cause" should be named "Reason"https://issues.rudder.io/issues/25312012-06-05T16:39:36ZJonathan CLARKEjonathan.clarke@normation.com
<p>Whenever we make in change in Rudder, we can now add a "reason" message thanks to <a class="issue tracker-2 status-5 priority-7 priority-lowest closed" title="User story: Change message for configuration changes (Released)" href="https://issues.rudder.io/issues/2399">#2399</a>. These reasons are output in the git commit message, and displayed in the Event Log view, under the column "Cause".</p>
<p>This should be renamed "Reason", to be consistent with other uses.</p> Bug #2530 (Released): Prevent the move of a Technique in Active Library if it's already present i...https://issues.rudder.io/issues/25302012-06-05T16:37:03ZJean VILVERjean.vilver@normation.comBug #2528 (Released): Providing a reason for a change should not be mandatory by defaulthttps://issues.rudder.io/issues/25282012-06-05T16:16:31ZJonathan CLARKEjonathan.clarke@normation.com
<p>The "change message" feature introduced by <a class="issue tracker-2 status-5 priority-7 priority-lowest closed" title="User story: Change message for configuration changes (Released)" href="https://issues.rudder.io/issues/2399">#2399</a> asks for a reason for each change, that is saved as a "commit" message. This can be mandatory or not.</p>
<p>However the default setting is "false" (ie, not mandatory) but the default in the config file provided is "true".</p> User story #2525 (Released): Update supported OSeshttps://issues.rudder.io/issues/25252012-06-05T07:26:19ZJonathan CLARKEjonathan.clarke@normation.com
<p>The docs currently state the server only runs on Debian GNU/Linux 5 (Lenny), Debian GNU/Linux 6 (Squeeze) and SuSE Linux Enterprise Server (SLES) 11 SP1 although we now support a whole list of OSes for the server:</p>
<ul>
<li> Debian 5</li>
<li> Debian 6</li>
<li> RHEL/CentOS 6</li>
<li>Ubuntu 11.10</li>
<li>Ubuntu 12.04</li>
<li>SLES 11</li>
</ul> Bug #2521 (Rejected): When ugrading the surder-server-root packages, the Techniques are automatic...https://issues.rudder.io/issues/25212012-06-04T15:50:54ZNicolas CHARLESnicolas.charles@rudder.io
<p>I upgraded rudder-server-root from a 2.4.0.git to a later 2.4.0.git, and all my customized technique were replaced in the /var/rudder/configuration-repository were replaced, without any question nor warning from the packaging script.</p>
<p>The commit message is :<br /><pre>
Upgrade system Techniques - automatically done by rudder-upgrade script
</pre></p> User story #2501 (Released): Show a popup input to explain move between Reference Technique Libra...https://issues.rudder.io/issues/25012012-05-29T10:56:45ZJean VILVERjean.vilver@normation.comBug #2495 (Released): Bad way to find EventLog to migrate from Rudder 2.3https://issues.rudder.io/issues/24952012-05-22T08:50:31ZFrançois ARMANDfrancois.armand@rudder.io
<p>The current way to choose event logs to migrate in the Scala code is to use the SQL query defined in <a class="external" href="http://www.rudder-project.org/redmine/issues/2364#note-1">http://www.rudder-project.org/redmine/issues/2364#note-1</a> - but as explained in following comments, that query is not supported in older Postgres version.</p>
<p>=> find an other way to choose event logs to migrate</p> User story #2494 (Released): Add reasons field to groups edit formhttps://issues.rudder.io/issues/24942012-05-21T16:44:58ZJean VILVERjean.vilver@normation.comUser story #2493 (Released): Add reasons field to Directives edit formhttps://issues.rudder.io/issues/24932012-05-21T16:44:17ZJean VILVERjean.vilver@normation.comUser story #2492 (Released): Show a popup input to explain delete or disable in Rules, Directives...https://issues.rudder.io/issues/24922012-05-21T16:37:59ZJean VILVERjean.vilver@normation.comUser story #2490 (Released): Add reasons field to rule edit formhttps://issues.rudder.io/issues/24902012-05-14T16:40:36ZJean VILVERjean.vilver@normation.com
<p>Add reasons field to rule edit form.</p>
<p>This is a frontend for <a class="issue tracker-2 status-5 priority-7 priority-lowest closed" title="User story: Change message for configuration changes (Released)" href="https://issues.rudder.io/issues/2399">#2399</a>.</p> User story #2489 (Released): Add dbMigration-2.3-2.4-add-EventLog-reason-column.sql to 2.4 migrat...https://issues.rudder.io/issues/24892012-05-11T16:50:32ZFrançois ARMANDfrancois.armand@rudder.io
<p>When <a class="issue tracker-2 status-5 priority-7 priority-lowest closed" title="User story: Change message for configuration changes (Released)" href="https://issues.rudder.io/issues/2399">#2399</a> will be completed, a new column in the eventlog table will be needed: "reason".</p>
<p>A migration script was created to add it from a 2.3 database in rudder-core/src/main/resources/Migration/dbMigration-2.3-2.4-add-EventLog-reason-column.sql</p>
<p>That script must be called in the migration script if the EventLog table does not already have a "reason" column.</p> Bug #2487 (Released): When a not known os is given, the report parsing does not fails earlyhttps://issues.rudder.io/issues/24872012-05-10T16:25:38ZFrançois ARMANDfrancois.armand@rudder.io
<p>When we try to parse an inventory for a node with a not know OS, the report parsing succed, but no OS Type is associated, what is impossible.</p>
<p>We must fails with a "OS not supported" error (or something like that).</p>
<p>Reproduce: set <OPERATINGSYSTEM><NAME>XXX</NAME>...</p>
<p>And try to add the report: nothing say that the OS is not supported, but the inventory can not be added.</p> User story #2486 (Released): Add better error reporting when a node can not be addedhttps://issues.rudder.io/issues/24862012-05-10T16:02:47ZFrançois ARMANDfrancois.armand@rudder.io
<p>When a node with a non-known OS name is added, we get a message:</p>
<p>"17:57:34.677 [Thread-18] ERROR org.slf4j.LoggerFactory - Report processing will be incomplete, found error: Can not add tree: nodeId=c23035cb-431b-4939-9b05-9b663adbc32f,ou=Nodes,ou=Pending Inventories,ou=Inventories,cn=rudder-configuration"</p>
<p>We at least want to have the root cause of that problem.</p>