Project

General

Profile

2.4.0~alpha7

closed

2012-06-06

100%

56 issues   (56 closed — 0 open)

Time tracking
Estimated time 10.00 hours
Issues by
Bug

28/28
User story

22/22
Architecture

6/6
Related issues
Bug #2068: Some queries are overly slow Actions
Bug #2093: When a Node is deleted, or a Node is accepted in Rudder and something bad happen, the Machine on which the Node is is always deleted Actions
Bug #2304: spec compatibility for centos6 Actions
Bug #2305: Install failed for rudder-reports rpm on centos6 Actions
Bug #2306: rudder-webapp: apache2 don't exist on centos6 Actions
Bug #2361: Eventlog not correctly renamed Actions
Bug #2370: Remove "userlib_" in generated id for active technique Actions
Bug #2373: Left menu in node management uncorrectly displayed. Actions
Bug #2376: The rudder-webapp package has wrong apache related dependencies on RHEL like systems (should be httpd instead of apache2) Actions
Bug #2377: On CentOS/RHEL 6, Rudder detects two running syslog daemons and, confused, outputs an error Actions
Bug #2378: rudder-reports.spec compatibility for centos6 : bad require for rsyslog module pgsql Actions
Bug #2382: Centos6 : Apache config failed in rudder-webapp.spec Actions
Bug #2386: Rudder seems to have difficulties with funky chars in Rules names Actions
Bug #2389: rudder-upgrade : error while initialising rudder rsyslog config on fresh installs Actions
Bug #2396: It seems that on Ubuntu, perl-prepare.sh script used for building rudder-agent has some problems with ld Actions
Bug #2405: rudder packages for Ubuntu doesn't seem to be functionnal (especially Jetty) Actions
Bug #2412: The system technique for the policy server doesn't update the rsyslog.conf configuration on Ubuntu Actions
Bug #2421: The CheckDit at startup only checks the presence of requiered entry, and does not try to repair Actions
Bug #2436: Rudder packages are built for CentOS 6 but this CentOS 5 is still failing. Actions
Bug #2439: rudder-inventory-ldap package: we don't need no more to specify version for BerkeleyDB on supported Debian-like OS Actions
Bug #2449: Align all event log IDs in the table Actions
Bug #2487: When a not known os is given, the report parsing does not fails early Actions
Bug #2495: Bad way to find EventLog to migrate from Rudder 2.3 Actions
Bug #2521: When ugrading the surder-server-root packages, the Techniques are automatically replaced by the one shipped in the packages Actions
Bug #2528: Providing a reason for a change should not be mandatory by default Actions
Bug #2530: Prevent the move of a Technique in Active Library if it's already present in this tree Actions
Bug #2531: Event log column "Cause" should be named "Reason" Actions
Bug #2532: When deleting a Rule, the reason input is not output to the change log in git Actions
User story #1988: When the postgresql database is restarted, the application is not usable anymore Actions
User story #2094: When we remove a Node from Rudder, save its information in a "Removed inventories" branch of LDAP Actions
User story #2296: Build an update script to change existing eventLog after item renaming Actions
User story #2329: Packages for RHEL/CentOS 6 Actions
User story #2338: Packages for Ubuntu Actions
User story #2355: Allow user to add a message when archiving Actions
User story #2366: The base.url parameter of rudder-web.properties is not necessary anymore Actions
User story #2372: Clean up old outputs from CFEngine directory Actions
User story #2381: Create an administration page to manage the database Actions
User story #2399: Change message for configuration changes Actions
User story #2422: Create a migration script for ldap-inventory and rudder to add entries in the ldap trees and update the configuration.properties files Actions
User story #2431: Drakkar logo for Rudder 2.4 Actions
User story #2442: Merge the core-lib.st and library.st files Actions
User story #2450: Add "Reload Techniques" to the Administration screen Actions
User story #2486: Add better error reporting when a node can not be added Actions
User story #2489: Add dbMigration-2.3-2.4-add-EventLog-reason-column.sql to 2.4 migration script Actions
User story #2490: Add reasons field to rule edit form Actions
User story #2492: Show a popup input to explain delete or disable in Rules, Directives and Techniques Management Actions
User story #2493: Add reasons field to Directives edit form Actions
User story #2494: Add reasons field to groups edit form Actions
User story #2501: Show a popup input to explain move between Reference Technique Library to Reference Active Library Actions
User story #2525: Update supported OSes Actions
Architecture #2364: Test for the XML fileformat in migration script for EventLog migration in DB Actions
Architecture #2392: CSS ameliorations in rudder webapp Actions
Architecture #2397: Clarify download options on web site and in documentation Actions
Architecture #2420: Update to specs 1.9 Actions
Architecture #2434: Isolate postgres data used for test Actions
Architecture #2445: Upgrade OpenLDAP that we package to 2.4.30 Actions

Also available in: TXT