# 2.4.8 2013-09-02 [BROKEN Release] Maintenance release 8 for 2.4 version * Bug #1175: Techniques "Package management for RHEL / CentOS / SuSE / RPM systems" and "Package management for Debian / Ubuntu / APT systems": Always report success, even on repair * User story #2958: Explain how to migrate a server to another machine * User story #3009: Create a usage handbook that summarize common usage scenarios in Rudder * User story #3084: Create a Technique library upgrade documentation * User story #3115: Technique "Download From A Shared Folder": Add possibility to set SUID and SGID to files copied * User story #3378: Technique "Group management": make group creation optional * User story #3444: Technique "Package management for RHEL / CentOS / SuSE / RPM systems": Improve performances of the Technique * User story #3445: Clean classes expression in rpmPackageInstallation * User story #3451: Read data from external file in download from shared folder * Bug #3531: Backport the git lock erase promise if older than 5 minutes from 2.5 to 2.4 * Bug #3566: Log permissions * Bug #3603: The files written by syslog in /var/log/rudder/reports/*.log and slapd in /var/log/rudder/ldap/slapd.log are still empty after a logrotate * Bug #3624: /etc/crontab duplicate entries on debian * Bug #3634: The Rudder agent post installation and removal scripts are not cleaning things correctly * Bug #3636: No Answer status with multiple instanced of cfexecd * Bug #3721: Error on Rudder about lack of RAM memory should be explicit * User story #3778: Make group creation optionnal in group management * Bug #3779: Technique "Package management for RHEL / CentOS / SuSE / RPM systems" v4.0: Technique uses wrong path for data file (3.0/...) * Bug #3781: The XML parser which check metadata.xml of the Techniques display a wrong error message when the XML is malformed (Talk about SECTION when it is due to INPUTS) * Bug #3810: The properties 'history.inventories.enable' and 'ldap.inventories.removed.basedn' are missing the /opt/rudder/etc/inventory-web after a migration from Rudder 2.3 and 'history.inventories.enable' is uslessly added into /opt/rudder/etc/rudder-web.properties * Bug #3813: /opt/rudder/bin/rudder-upgrade requires rsync but no package depends on it * Bug #3815: Technique "Package management for RHEL / CentOS / SuSE / RPM systems": Package installation using yum doesn't work (RPM based systems like Red Hat / CentOS) * Bug #3816: Technique "Package management for RHEL / CentOS / SuSE / RPM systems": Typos related changes - refs #1175 * User story #3831: Add Informations about the rsync modules of rudder-project * Bug #3834: Inventory doesn't support Scientific Linux - Os Name = Red Hat * Bug #3835: OS Full name should be queriable * Bug #3836: Missing support for OS "Scientific linux" and "Unbreakable Linux" * Bug #3837: Rudder doesn't support Oracle Linux - Can't merge inventory in LDAP * Bug #3839: Add correct display name for Scientific Linux and Oracle Linux * Bug #3842: On Node 'Management>Groups' Screen modifying a group let the "Save" button masked and let believe it as not clickable (which is not true) * Bug #3853: On node search, regex filter on attribute not in node summary is broken with "OR" * User story #3858: Technique "Download From A Shared Folder": Add possibility to set SUID and SGID to files copied (transition to Rudder 2.8) * Bug #3861: Error when deleting category * Bug #3864: The logrotate file of Debian and Ubuntu is duplicated since the name from the packaging is wrong * Bug #3865: rudder-upgrade prints an unnecessary warning: "WARNING: Some event log are still based on an old file format (file format 1), please upgrade first to 2.6 to make this migration" * Bug #3866: On node search, "OR" and "include policy server" leads to 0 results * Bug #3870: Technique "Sudo utility configuration": Technique is not correctly reporting when applied by multiple rules * Bug #3872: Groups screen: Using storage criteria lead to an error caused by the Unit format * Bug #3880: Errors when accepting/refusing nodes are ignored * Bug #3883: The limit of the eventlog length (64chars) could lead to SQL errors * Bug #3885: Event logs can't be saved when the Actor name is more than 64 chars long * Bug #3890: Remove virtual limitation on the user name in the database * Bug #3891: Create a migration script for name length limitation * Bug #3896: The postrm script of Rudder-agent removes too much files * Bug #3899: Backport the git lock erase promise if older than 5 minutes from 2.5 to 2.4 (Implementation)