<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
We are proud to announce the availability of new version of Rudder,
2.4.0~rc1.<br>
<br>
This is a release candidate for 2.4.0 version. It contains the
following list of bug fixes and changes compared to 2.4.0~beta5:<br>
<br>
As always, check out
<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/foswiki/bin/view/Download/WebHome">http://www.rudder-project.org/foswiki/bin/view/Download/WebHome</a> for
download links.<br>
<br>
***** Bug fixes *****<br>
<br>
******* Core *******<br>
<br>
Fix reporting when the only node of a Rule has been deleted
(#2937)<br>
Fix download of Directives/Rules/Groups as zip from Rudder UI
(#2990)<br>
Fix system Technique common: The Technique used an unsupported
parameter on Windows (#2954)<br>
Various code fixes (#2934)<br>
<br>
******* UI *******<br>
<br>
Fix IE9 Compatibility (#2027, #2028, #2029)<br>
Various UI Fixes (#1957, #2936, #2979, #2980, #2981, #2982,
#2991, #2992, #3010)<br>
<br>
******* System integration *******<br>
<br>
Prevent Rudder agent from writing many logs to local syslog
(/var/log/syslog or /var/log/messages on each node) (#2993)<br>
Save disk space by compressing big log files - copy of reports
on server (#2962)<br>
Save disk space by compressing big log files - autoclean LDAP
database transaction logs (#2963)<br>
Fix broken Java dependencies on CentOS (#2941)<br>
Fix reporting on nodes with syslogd (not syslog-ng nor rsyslog)
which never communicated back to Rudder server (#2943)<br>
Add check to avoid any more than 5 cf-agents running
simulataneously (#3012)<br>
Fix cron check to relaunch CFEngine to detect cf-execd and
cf-agent too (#3013)<br>
Fix timestamp format in agent logs generated by the "failsafe"
mechanism (#2994)<br>
Prevent Jetty from hanging indefinitely when restart script
fails (#2846)<br>
<br>
******* Techniques *******<br>
<br>
Fix Technique "Job Scheduler": Job was never launched if start
time was between 0:00 and 9:00 AM (#2940)<br>
Fix Technique "Time Settings": Installation of NTP didn't work
on RHEL/CentOS (#2384)<br>
Fix Technique "Enforce a file content" version 2.0: this version
was not functional (#3022)<br>
Fix Technique "Package management for Debian / Ubuntu / APT
systems": avoid the package manager blocking on pre-existing
configuration files during package installation (#2946)<br>
<br>
***** Changes *****<br>
<br>
******* System integration *******<br>
<br>
This version of Rudder adds support for Debian Wheezy (7)<br>
<br>
******* Techniques *******<br>
<br>
Technique "User Management": Take into account network users
(special thanks to Michael Gliwinski!) (#2944)<br>
Test suite improvement (#2933)<br>
<br>
******* Documentation *******<br>
<br>
Add information on how to migrate a Rudder server to another one
(#2958)<br>
Various documentation fixes (#2340, #2942)<br>
<br>
***** Known issues *****<br>
<br>
There is one known issue with this release of Rudder:<br>
<br>
Technique "Enforce a file content" version 3.1 is rejected by
Rudder (#3027), causing the following bug fixes to be unavailable:<br>
Technique "Enforce a file content": Option to choose if the
file to edit should be created or not if it doesn't already exist
(#2945)<br>
Technique "Enforce a file content": line remplacement didn't
work if the replacement was empty and only one Directive from this
Technique was applied on a node (#2819)<br>
<br>
This can be worked around by downloading and installing a nightly
build of the rudder-techniques package, from our nightly build APT
repo (<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/apt-2.4-nightly/">http://www.rudder-project.org/apt-2.4-nightly/</a>) or RPM repo
(<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/rpm-2.4-nightly/">http://www.rudder-project.org/rpm-2.4-nightly/</a>).<br>
<br>
***** Release notes *****<br>
<br>
This version of Rudder is in release candidate status. This version
was focused on stabilization and system integration to be highly
reliable. While we have tested it thoroughly and believe it to be
free of any major bugs, use on mission-critical systems is not
encouraged at this time and is at your own risk. We are however
running it on several production systems with success.<br>
<br>
***** Contributors *****<br>
<br>
Special thanks go out to the following individuals who invested
time, patience, testing, patches or bug reports to make this version
of Rudder better:<br>
<br>
Benoît Peccatte<br>
François Bayart aka A-Kaser (Look a box)<br>
Michael Gliwinski (Henderson Group)<br>
<br>
We are impatient to hear your feedback, be it comments on this blog,
questions on Twitter, bug reports or feature requests or even GitHub
pull requests!<br>
<br>
See also this announcement online:<br>
* Changelog:
<a class="moz-txt-link-freetext" href="http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24">http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24</a><br>
* Twitter: <a class="moz-txt-link-freetext" href="https://twitter.com/RudderProject">https://twitter.com/RudderProject</a> <br>
<pre class="moz-signature" cols="72">--
==========================================
Nicolas PERRON
------------------------------------------
Normation
87 rue de Turbigo, 75003 Paris, France
------------------------------------------
Telephone: +33 (0)1 83 62 56 79
Mobile: +33 (0)6 24 79 31 79
------------------------------------------
Web: <a class="moz-txt-link-freetext" href="http://www.normation.com/">http://www.normation.com/</a>
==========================================</pre>
</body>
</html>