Change logs for Rudder 2.10
Rudder 2.10 has reached End of Life the 5th December 2015. This version is codenamed ``Catamaran''.
This page provides a summary of changes for each version. Previous beta and rc versions are listed below for convenience.
Main new features in Rudder 2.10:
-
Lots of performance and scalability improvements:
-
Promises generation is much faster
-
Removed unnecessary commits to database
-
Overloaded Inventory endpoint does not impact Web Interface anymore
-
Improve CFEngine server promises
-
Do not keep redundant logs
-
-
Configure agent run interval (from 5 minutes to 6 hours) directly from webapp
-
More flexibility when selecting Rule targets, you can now exclude some groups
-
Get all inventory datas from a node using the REST API
-
Rudder agent is now supported on AIX 5.3+
-
Various improvements on packaging, refactoring and small UI fixes
A blog post (only in French for now) about all these features is available here: http://blog.normation.com/fr/2014/05/18/rudder-2-10/
Installing, upgrading and testing
Documentation to Install and Upgrade is available online. The Download page sums up URLs. We also recommend using the Rudder Vagrant config if you want a quick and easy way to get an installation for testing.
If you upgrade from 2.8x, 2.9.x or 2.10..x to 2.10.5, there is a specific upgrade procedure:
\1. Update the Rudder packages (yum update ``rudder-*'' or apt-get install rudder-server-root
\2. Restart the Web Interface ( /etc/init.d/rudder-jetty restart ), and wait for it to be fully started, and then click on ``Update'' on the top right hand side corner to trigger Policy update
\3. Update the ncf package (yum update ncf or apt-get install ncf)
New installations or upgrades from 2.6.x are not impacted by the issue.
Operating systems supported
This version provides packages for these operating systems:
-
Rudder server: Debian 5, Debian 6, Debian 7, RHEL/CentOS 6, SLES 11, Ubuntu 12.04, Ubuntu 12.10
-
Rudder agent: all of the above plus RHEL/CentOS 3, RHEL/CentOS 5 and SLES 10
Rudder 2.10.20 (2015-12-10)
Bug fixes
API
-
Fixed: API Parameters create ``overridable'' boolean check doesn’t work (#6695)
Web - Config management
-
Fixed: Read technique access does not give access to techniques (#7514)
Server components
-
Fixed: promises are not regenerated when a node is transformed into a relay (#7301)
Agent
-
Fixed: rudder-agent repository on GitHub does not have a license (#7394)
Initial promises & sys tech
-
Fixed: Use whole path to binaries in cron from check-rudder-agent on AIX (#7525)
-
Fixed: Erroneous use of ``\&'' in initial promises (#7517)
-
Fixed: Use of nonexistant class cfengine_community makes failsafe.cf not copy CFEngine binaries to /var/rudder (#7499)
-
Fixed: ``Update'' component of common technique sometimes return unexpected status and has incomplete reporting (#6648)
-
Fixed: Syslog fails to restart due bad line in syslog-ng.conf (#7389)
Architecture - Refactoring
-
Fixed: Correct a warning in rudder compilation (#7356)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
François Bayart
-
Steeve Chailloux
-
David Durieux
-
Fabrice Flore-Thébault
-
Janos Mattyasovszky
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.19 (2015-10-27)
Bug fixes
Web - Nodes & inventories
-
Fixed: Link from node/directive list to node detail is broken on Firefox (branch 2.10) (#7286)
Release notes
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.18 (2015-10-20)
Bug fixes
Initial promises & sys tech
-
Fixed: The daily cf-execd and cf-serverd restart should use SRC on AIX (#7274)
Techniques
-
Fixed: Ssh key distribution cannot distibute several keys on one user (#7254)
Release notes
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.17 (2015-09-24)
Bug fixes
Web - Config management
-
Fixed: Rules are not serialized correctly anymore (#7108)
Web - Compliance & node report
-
Fixed: Agent schedule is not historised, so we can’t know what was the agent run interval in the past (#7154)
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.16 (2015-08-19)
Bug fixes
Web - Compliance & node report
-
Fixed: Reporting cannot be used when there is several component with the same value and several messages (#7037)
Architecture - Refactoring
-
Fixed: Remove scala compiler warning about comparing values of type Null (#7072)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Janos Mattyasovszky
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.15 (2015-07-09)
Bug fixes
Web - UI & UX
-
Fixed: No rules displayed in firefox (#6490)
Web - Nodes & inventories
-
Fixed: ldap.attr.networkInterfaceDhcpServer in search node component (#6785)
Web - Config management
-
Fixed: After a partial promise generation, some nodes being a relay may have their promises stored in a non reachable location (#6729)
System integration
-
Fixed: Sometimes, promises get corrupted to the point they can’t be automatically repaired on a node (#6768)
Server components
-
Fixed: When a node is promoted to relay, the old rsyslog conf is never replaced (#6721)
Techniques
-
Fixed: Unexpected status for fileAlterationMonitoring (#6771)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
François Bayart
-
Olivier Mauras
This is a maintenance release, part of the 2.10 branch. An end-of-life date has been scheduled for this release (5th December 2015), See our FAQ for details, on the website. As such, it is recommended to upgrade all pre-2.11 installations to 2.11 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
Rudder 2.10.14 (2015-06-02)
Changes
Agent
-
Allow rudder server to remotely run the agent (#6553)
Bug fixes
Web - UI & UX
-
Fixed: Bad RegEx in Groups causes Server to not respond (#6680)
API
-
Fixed: In group API, attribute and comparator names are case sensitive (#6577)
Performance and scalability
-
Fixed: Do not check dns when checking promises (#6616)
Web - Nodes & inventories
-
Fixed: Error 500 when sending multiple files to inventory endpoint (#6508)
Packaging
-
Fixed: The detect_os.sh script is not valid (#6486)
Documentation
-
Fixed: Restore procedures has service name mistyped (#6664)
-
Fixed: Old Normation logo in the manual (#6643)
-
Fixed: Broken link in the demo section of rudder README (#6610)
-
Fixed: Bibliography links are out of date (#6609)
-
Fixed: Broken links in the manual (#6607)
-
Fixed: Check spelling and grammar of the manual (#6599)
-
Fixed: Remove references to the Big Red Button in the manual (#6596)
-
Fixed: Fix asciidoc list formatting (#6595)
-
Fixed: Rudder Documentation typo (#6559)
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Janos Mattyasovszky
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.13 (2015-04-13)
Bug fixes
Techniques
-
Fixed: Please document usage of line replacement in Enforce a file content technique (#5979)
Initial promises & sys tech
-
Fixed: No reports for Propagate promises component on relay (#6404)
System integration
-
Fixed: rudder-jetty init script may fail on success (#5653)
Packaging
-
Fixed: Remove python dependency for rudder-agent (#6424)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Dennis Cabooter
-
Florian Heigl
-
Peter Keresztes
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.12 (2015-03-24)
Bug fixes
Techniques
-
Fixed: Enforce file content Technique doesn’t properly migrate lines from outside the zone to the zone (#6389)
Packaging
-
Fixed: AIX rudder-agent SPECfile fails to build due to a macro expansion error (#6380)
Architecture - Dependencies
-
Fixed: Upgrade Liftweb to v2.5.2 (security issue) (#6426)
Release notes
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.11 (2015-03-09)
Bug fixes
API
-
Fixed: Wrong default category set when creating a Rule (#6314)
Techniques
-
Fixed: it’s not possible to define variables with " in them in generic variable definition (#6279)
-
Fixed: Wrong reporting in Technique Enforce a file content if the file is not present (#6237)
-
Fixed: OpenSSH server technique tries to configure MaxSession on AIX 5.3, but this parameter is invalid on this OS (#6374)
-
Fixed: The fileManagement Technique does not report on AIX (#6362)
System integration
-
Fixed: The rudder-agent package should remove the inittab entry and subsystem on AIX, and should not run ldconfig (#6364)
Packaging
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Jean Cardona
-
Florian Heigl
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.10 (2015-02-06)
Changes
Tools
-
Server side debug for a single agent (#6180)
Techniques
-
Add post hook commands and working update for rpm package installation (#3857)
Bug fixes
Webapp - Display, home page
-
Fixed: Rudder stores too much or too big cookies, causing white page with HTTP status: 413: FULL head (#6146)
Webapp - Node management
-
Fixed: Cannot display software informations on accept new Nodes (#6155)
-
Fixed: When adding a line of search criteria, the category and field from the line above should be the same on the new line (#5905)
-
Fixed: Wrong error message when accepted an already accepted node (#4895)
-
Fixed: Can not move node groups with the form (#4571)
Webapp - Administration
-
Fixed: ``Server cannot be contacted at this time'' when tring to get Event Log details (#6172)
-
Fixed: Cleanup expected reports (#6150)
-
Fixed: Missing login eventlog (#6008)
-
Fixed: Deletion of a Rule will lead to a stacktrace into the diff of the related Change Request (#5374)
-
Fixed: It is overly slow to show the list of Pending Review or Pending Deployment even if the number is 0 (#4359)
-
Fixed: Jetty should compress the files rotated (/var/log/rudder/webapp/*.log) (#3916)
API
-
Fixed: Creating a directive via the api, makes it disabled by default (#6200)
-
Fixed: cannot use ``enabled'' json parameter in Directive API (#6176)
-
Fixed: Technique version cannot be specified with Directive API (#6174) ==== * Fixed: In API/rules include/exclude is ordered for target parameter (#5982)/redmine/issues/5389][#5389]])
Webapp - Reporting
-
Fixed: When two techniques generated with ncf-builder use the same generic method with same parameters, reporting cannot dinstinguish them, and reports ``Unknown'' (#5389)
Packaging
* Fixed: Error log when installing rudder-inventory ldap on RHEL6 #6032)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Alex Bruni
-
Dennis Cabooter
-
Florian Heigl
-
Lionel Le Folgoc
-
Olivier Mauras
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.9 ⇒ Not released, major bug in debian installation == (#6232)
Rudder 2.10.8 (2014-12-15)
Bug fixes
Webapp - Configuration management
-
Fixed: System rule are modified when trying to delete a directive (#5923)
-
Fixed: It should not be possible to delete system directives (#5875)
-
Fixed: Correctly display technique removed from source library (#5808)
-
Fixed: Description of default Rule ``Global configuration for all nodes'' is missing a space (#5788)
-
Fixed: On directive tree, tooltips does not appear anymore after directive update (#4223)
-
Fixed: Compliance percents are not sorted correctly (#5714)
Webapp - Display, home page
-
Fixed: Missing files on the load page (#5867)
Logging
-
Fixed: Rudder agents crons send far too many mails (#5190)
Documentation
-
Fixed: Rudder readme is totally out of date and irrelevant (#5926)
-
Fixed: User manual doesn’t explain how to use Parameters (#5729)
-
Fixed: Upgrade procedure in reference manual don’t upgrade ncf (#5285)
-
Fixed: The relay server docs don’t mention what do on nodes (#4365)
-
Fixed: Database maintenance chapter doesn’t mention automatic archiving (#3960)
System integration
-
Fixed: Require latest version of ncf including fixes for reporting (#5880)
-
Fixed: dpkg configure error prevents installing rudder-agent due to cf-serverd error (#5785)
-
Fixed: Use nxlog instead of Centreon E2S, as it has less dependencies, and installs on every windows (#5762)
-
Fixed: Call ncf configuration bundle from Rudder, to ensure configuration used is correct (#5597)
-
Fixed: We can configure the Configuration Repository folder in the config file of the Web Interface , but the system Techniques are enforcing the location /var/rudder/configuration-repository (#5347)
-
Fixed: Missing cfengine man pages (#4903)
AIX agent
-
Fixed: Technique SSHConfiguration don’t reports properly on Aix for component ``SSH start at boot'' if it is already correctly defined (#5902)
-
Fixed: Technique SSHConfiguration don’t reports properly on Aix for component ``SSH start at boot'' (#5860)
-
Fixed: Technique SSHConfiguration v4.0 fails on AIX - and stops agent execution (#5836)
-
Fixed: Messages sent from an AIX machine via a relay are not forwarded correctly (#5775)
Performance and scalability
-
Fixed: Ldap query to get all software by nodes take ages (#5803)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Dennis Cabooter
-
Florian Heigl
-
Lionel Le Folgoc
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.7 (2014-11-18)
Bug fixes
Techniques
-
Fixed: Technique `rpmPackageInstallation' v6.0 stores a file in the wrong directory (#5697)
-
Fixed: Permissions may be applied recursively even if not asked to by ``filesPermissions'' Technique (#5632)
-
Rudder is unable to compare two package version correctly (#5587)
-
Fixed: It’s not possible to update package to latest version (#5609)
-
Fixed: Packages are not updated correctly on redhat based systems (#5608)
-
Fixed: Zypper Management Technique doesn’t behave correctly, and should be splitted in two separated techniques (#5662)
-
Fixed: Multiline header is added at each run on managed files (#4650)
-
Fixed: Zypper technique says skipping but returns UNKNOWN. (#5493)
-
Fixed: Generic variables definition forbid `&' character usage (#5605)
-
Update all techniques to respect normal ordering (#5306)
-
Fixed: Acceptance tests are failing on some techniques (#5752)
-
Fixed: On 2.11 rudder-agent, ``Repair'' status is always defined, even if nothing is modified (#5327)
Webapp - CFEngine integration
-
Fixed: Two techniques with the same ID leads to strange error about git tree ids (#5614)
Performance and scalability
-
Fixed: Webapp checking that CFEngine variables used in Directive are correct takes too much time at startup (#5358)
Miscellaneous
-
Fixed: cf-clerk does not compile with Java 8 (#5657)
Windows integration
-
Fixed: list-comptabile-inputs doesn’t work on windows (#5616)
-
Fixed: executor daemon command needs to be different on windows for it to work (#5594)
-
Fixed: System technique make cfengine enterprise copy binairies from /opt/rudder, killing itself (#5590)
-
Fixed: Handling of inventory fails on Windows (#5588)
-
Fixed: The repository for modified files is not activated on Windows (#5581)
-
Fixed: Ports used for file copy between Client and Server is not correct on Windows, preventing copy on Windows (#5431)
-
Fixed: remove use of proxy in curl on Windows, as it is an invalid option (#5429)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Dennis Cabooter
-
Matthieu Ca.
-
Florian Heigl
-
Lionel le Folgoc
-
Olivier Mauras
-
Alex Tkachenko
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.6 (2014-09-24)
Bug fixes
Techniques - Sys & init promis
-
Fixed: Tools folder are empty! (#5564)
-
Fixed: Cache generated by list-compatible-inputs is cleared by the ncf copy, resulting in perpertual repaired state (#5513)
-
Fixed: The script list-compatible-inputs, copied from ncf, cannot be copied as the path is invalid (#5512)
-
Fixed: System techniques on Windows try to schedule a cron task (#5441)
-
Fixed: command to run fusion-inventory on windows fails due to parsing error in command line (#5430)
-
Fixed: Rewrite initial promises to use normal ordering on 2.10 (#5498)
Techniques
-
Fixed: clock management technique always report repair on Windows (#5341)
-
Fixed: User Management Techniques don’t reports properly on Windows (#5340)
-
Fixed: The Rudder logrotate configuration is not in sync between regular and initial promises (#5544)
-
Fixed: use list-compatible-inputs from ncf, not from tools (#5527)
-
Fixed: Call list-comptible-inputs with /bin/sh (#5519)
-
Fixed: Rewrite techniques to use normal ordering on 2.10 (#5507)
-
Fixed: downloadFile.st contains a syntax error (#5457)
-
Fixed: SSH Configuration Technique does not make timestamped version of all the version of the ssh config file, like other techiques (#5344)
-
Fixed: The Rudder logrotate configuration uses the wrong argument to reload rsyslog on Debian Wheezy (#5486)
-
Fixed: Add a placeholder for new technique on old versions (#5463)
Webapp - Config management
-
Fixed: Correct HTML: badly closed tag (#5540)
Packaging
-
Fixed: The strict dependency on ncf in rudder-techniques need to be updated (#5545)
-
Fixed: remove list-compatible-inputs from tools (#5532)
-
Fixed: rudder-techniques should require a specific version of ncf (#5522)
-
Fixed: Upgrade rudder-agent can fail if cf-serverd/cf-execd fails to stop gracefully (#4387)
Documentation
-
Fixed: Do not use contrib and non-free (#5181)
Release notes
This is a bug fix release in the 2.10 series. All installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.5 (2014-08-28)
Release notes
If you upgrade from 2.8x, 2.9.x or 2.10..x to 2.10.5, there is a specific upgrade procedure:
\1. Update the Rudder packages (yum update ``rudder-*'' or apt-get install rudder-server-root
\2. Restart the Web Interface ( /etc/init.d/rudder-jetty restart ), and wait for it to be fully started, and then click on ``Update'' on the top right hand side corner to trigger Policy update
\3. Update the ncf package (yum update ncf or apt-get install ncf)
New installations or upgrades from 2.6.x are not impacted by the issue.
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.4 (2014-08-13)
Bug fixes
Techniques
-
Fixed: The find call used to get all the files to include in the CFEngine run is not usable on AIX (#5292)
-
Fixed: Inventory are not correctly generated on Windows (#5342)
-
Fixed: Agent run may fail on nodes because some promises have not be correctly updated (#5231)
-
Fixed: fstab Tehcnique empties all options with Rudder 2.11 (#5328)
-
Fixed: In checkGenericFileContent v5.0, no answer in post modification hook (#5318)
-
Fixed: In checkGenericFileContent v5.0, reporting on post modification hook can be unknown (#5312)
-
Fixed: User Management 3.0 reports No Answer for the password component if the password is not set (#5239)
-
Fixed: CheckGenericFileContent does not send reports for post modification hook when we enforce the content of the file only at creatio (#5208)
-
Fixed: Incorrect use of commands without their full path in Sudo Parameter technique (#5187)
-
Fixed: We can’t set the SUID/SGID in technique Manage file and folders (#5325)
-
Fixed: Process management technique uses invalid syntax on CFEngine 3.5+ (#5315)
Web application
-
Fixed: Changes in directives are not taken into account if we only change the case of characters (#5317)
-
Fixed: The table reportsexecution, storing the agent execution on every node, is never emptied, and so can get very big (#5326)
-
Fixed: When using several times a generic_method on same file with class_prefix based on filename, reports will be in
Unknown'' and
No answer'' status (#5330) -
Fixed: Popup content can be displayed outside of popup if content grow after intiialisation (#5314)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Florian Heigl
-
Lionel Le Folgoc
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.3 (2014-07-01)
Bug fixes
Webapp - Config management
-
Fixed: Cannot open Rule details when a Group contains a quote in its name (#5068)
Techniques
-
Fixed: In User Management Technique v3.0, if the group is not defined, the user is not created because it tries to insert it in group "" (#5149)
-
Fixed: Sudo techniques can fail on Debian 6 if the original files defines Command aliases (#5140)
-
Fixed: OpenSSH Techniques (debian3, 4, centos3 and 4): typo in class names for OS version (#5136), do not set invalid parameters (#5126, (#5127), cannot configure SSH Server on boot (#5144)
System integration
-
Fixed: Demo data generates nodes with Nova hosts, but no ``demo'' license is set, so promises generation fails (#5169)
-
Fixed: Rsyslog conditonnal cannot accept reports from CFEngine 3.6 (#5099)
-
Fixed: The script /var/rudder/tools/check_rsyslog_version will not work with versions containing more digits like ``5.10.1'' (#4757)
-
Fixed: Migration script `rudder-upgrade-database' displays unwanted logs (#5125)
Relay Servers
-
Fixed: The UUID passed to rudder-node-to-relay is case sensitive, and using wrong case renders the node invisible in webapp (#5053)
Webapp - Reporting
-
Fixed: On reports (Rule,Node) pages, a warning is displayed in javascript console (#5111)
Packaging
-
Fixed: check-rudder-agent fails if an error occurs during sourcing /etc/profile (#5119)
API
-
Fixed: Can’t pass correctly json parameter to group API (#5122)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Cédric Jardin
-
Lionel Le Folgoc
-
Daniel Stan
This is a bug fix release in the 2.10 series and all installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version. When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.2 (2014-06-12)
Bug fixes
Techniques
-
Fixed: Technique rpmPackageInstallation: Specified version is not taken into account (#4999)
-
Fixed: Technique sshKeyDistribution: ssh keys are not added or replaced if they don’t finish by equal sign (#4719)
-
Fixed: Technique groupManagement: Members of group are enforced at group creation even if option is not set (#5001)
-
Fixed: Technique User management: cannot create an user if a group using the same name already exists (#4270)
Techniques - Sys & init promis
-
Fixed: Initial promises on server cause an error to be logged due to duplicate ``empty_file_before_editing'' setting (#5003)
-
Fixed: Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5) (#4996)
-
Fixed: Windows clients may run the execRun command several times - for cygwin and plain windows cases (#4975)
-
Fixed: Date/time is not defined on all reports in failsafe.cf from initial promises (#4966)
-
Fixed: RHEL 3 and 4 don’t report correctly due to ``/bin/date: unrecognized option `–rfc-3339=second’'' (#4963)
-
Fixed: Initial promises don’t fetch new promises anymore on the policy server (#4992)
-
Fixed: cf-agent complains about removed constraint `host_licenses_paid' (#4970)
-
Fixed: Typo in site.st causes promise generation to fail (#5004)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Fabrice Flore-Thébault
-
Cédric Jardin
-
William Ott
This is a bug fix release in the 2.10 series. All installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.1 (2014-06-06)
Bug fixes
Webapp - Config management
-
Fixed: If we select a Rule category (other than top) then reload the Rule page, the state of the Rule table is not coherent. (#4947)
-
Fixed: Rule category can be deleted after the a Rule was added to the category (#4946)
-
Fixed: In Rule grid, mouse hover on ``Not applied'' Rules display a wrong tooltip (#4787)
-
Fixed: A policy generation may occur when nothing has changed (#4859)
-
Fixed: Missing ``Unix Crypt Des'' algo type for AIX password (#4785)
Webapp - Reporting
-
Fixed: Reports cannot be inserted into postgresql due to a limit on ids (#4831)
Webapp - CFEngine integration
-
Fixed: Unconsistencies on generated promise due to bug on comparison logic between them (#4878)
Techniques
-
Fixed: CheckGenericFileContent can have several ``repaired'' status on each of the different component, even is the end state is convergent (#4805)
-
Fixed: Technique ``Package management for Debian / Ubuntu / APT systems'', typo in the option to install an earlier package (#4754)
-
Fixed: Rudder causes RHEL nodes to be blacklisted in RHN due to intensive yum usage (#3855)
-
Fixed: Job Scheduler Technique should not use ifelapsed to avoid running several time same job (#4841)
-
Fixed: Technique ``APT package manager configuration'': Rudder file header is not added correctly in repository files (#4809)
-
Fixed: Technique ``Download a file from the shared folder'' fails to report correctly on AIX (#4764)
-
Fixed: Adapt Techniques to support Android in 2.10 (#4741)
-
Fixed: On AIX, several techniques try to use the group ``root'' (#4705)
Techniques - Sys & init promis
-
Fixed: cf-agent slowed by users addition into inventory and displays a lot of warnings about that (#4932)
-
Fixed: Automatic reparation method for cf_lock. is only checked once an hour (#4812)
-
Fixed: Reports are not inserted into Rudder because regexp in rsyslog is too greedy when matching execuction timestamp (#4761)
-
Fixed: The initial promises use a remote copy which does not permit the copy of ncf files to /var/rudder/ncf/ and generation of promises fails. (#4894)
-
Fixed: Copy of ncf files on the Policy Server leave removed files, resulting in duplicate promises if we rename or move files (#4837)
-
Fixed: CFEngine complains about a Typo in policy_server initial promises (#4745)
-
Fixed: The Techniques should use user crontabs on AIX instead of cron.d (#4907)
-
Fixed: Add skipidentify cofniguration on Android devices (#4749)
-
Fixed: initial promises don’t detect basic Rudder inventory requirements (machine ID, CFEngine key, CFEngine user, users…) on non Linux/Windows/Android systems (#4696)
-
Fixed: Reports from AIX nodes don’t get parsed due to an erroneous date format (#4703)
-
Fixed: syslogd support partially broken: ``*'' is not always supported for priority, and reload command varies on AIX (#4702)
-
Fixed: cf-agent fails on systems that don’t support ``find . -not …'' (AIX, in particular) (#4700)
-
Fixed: Rudder Techniques try to call miniperl with a wrong authenticate argument (#4825)
-
Fixed: There are StringTemplate variables in the initial-promises (#4824)
-
Fixed: The script /var/rudder/tools/check_rsyslog_version will not work without absolute path of rsyslogd (#4758)
-
Fixed: The initial promises are missing a class definition for force_inventory when /opt/rudder/etc/force_inventory is here (#4765)
-
Fixed: Permit script check_rsyslog_version to stop if an error is encountered (#4869)
-
Fixed: policy_server.dat file is not read on Nodes if its size exceed 40 bytes (#4921)
Packaging
-
Fixed: Rudder init script may not correctly initialize policy_server.dat file, resulting in a non functioning Rudder server (#4915)
-
Fixed: An AIX selection condition is wrong in rudder-agent SPECfile (#4957)
-
Fixed: AIX rudder-agent packages are missing a dependency against tokyocabinet (#4951)
-
Fixed: The check-rudder-agent fix of cf_lock uses echo -n, which is incompatible with AIX (#4925)
-
Fixed: The rudder-webapp post installation script tries to call /etc/init.d/jetty instead of rudder-jetty on Debian based systems (#4920)
-
Fixed: check-rudder-agent should source /etc/profile before starting (#4908)
-
Fixed: The rudder-agent package tries to use an broken pre-installation script on AIX (#4886)
-
Fixed: rudder-agent RPM packages do not detect AIX properly in some cases (#4879)
-
Fixed: rudder-agent package build fails on debian-type OS because it can’t find FusionInventory code (#4830)
-
Fixed: The rudder-agent postinstall script tries to backup sysV type init scripts on AIX (#4801)
-
Fixed: AIX service management for rudder-agent has some bugs (#4704)
-
Fixed: RPM postinst and check-rudder-agent fail on AIX because our ``uuidgen'' is not executable (#4698)
-
Fixed: On AIX, check-rudder-agent script complains uses nonexistant options for ps and echo (#4695)
System integration
-
Fixed: rudder-agent may be stucked by tokyo cabinet database bloating (#4769)
-
Fixed: Default file header should be one liner to prevent header repetition. (#4755)
-
Fixed: cf_lock.tcdb is not cleaned by check-rudder-agent script when update file is older than 10 minutes (#4752)
-
Fixed: Typo in /opt/rudder/bin/check-rudder-agent, prevent cleaning of cf-lock and floods with cron mails (#4686)
-
Fixed: rudder agent is restarted by the cron job even if /opt/rudder/etc/disable-agent is present (#4688)
-
Fixed: A race condition may occur during rudder-server-root initialisation (#4635)
-
Fixed: The script rudder-init.sh should not output CFEngine execution, and keep the output of all commands in the log (#4634)
-
Fixed: When multiples cf-execd are running at the same time, agent is not behaving properly, and node is in NoAnswer state (#4613)
-
Fixed: check-rudder-agent does not adapt it’s check rate to the agent frequency (#4766)
Inventory (webapp, Fusion)
-
Fixed: Solaris Node are not correctly identified by Rudder inventory process (#4701)
-
Fixed: Network interface sharing the ip address are ignored by the inventory parser (#4883)
-
Fixed: Process start date are displayed as ``bad format'' in Rudder web interface (#4742)
-
Fixed: FusionInventory may report duplicated Network interfaces on AIX system, causing Rudder to ignore them (#4882)
-
Fixed: Get Technology Level and Service pack from AIX inventories (#4727)
-
Fixed: Add missing information about microcode version of Power system in AIX (#4725)
-
Fixed: processes start date in AIX inventory displayed as "Bad format’ (#4721)
-
Fixed: Inventories from AIX machines fail with ``invalid structural object class chain (aixNode/unixNode)'' error (#4699)
-
Fixed: Rudder does not report the Virtual Machine type correctly on AIX LPARs (#4826)
Logging
-
Fixed: A developpment log line is displayed when saving Directive edit form (#4660)
Miscellaneous
-
Fixed: Typo in rudder-commons project, display a warning when compiling (#4853)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Cédric Cabessa
-
Dennis Cabooter
-
Fabrice Flore-Thébault
-
Mikaël Mantel
-
Olivier Mauras
This is a bug fix release in the 2.10 series. All installations of 2.10.x should be upgraded when possible. It is recommended to upgrade all pre-2.10 installations to 2.10 as soon as possible to enjoy the latest features and improvements of a more mature and stable version.
When we release a new version of Rudder it has been thoroughly tested, and we consider the release enterprise-ready for deployment. This version is declared ``stable'' since it has proven itself to be stable in production over a period of several months following general availability of the release.
Rudder 2.10.0 (2014-03-28)
Changes
Webapp - Administration
-
Harmonize display of new parameters with others in `Settings' page (#4668)
Documentation
-
Fixed: Update references in documentation to Rudder 2.10 (#4715)
Bug fixes
Webapp - Configuration
-
Fixed: Editing a Directive, after creating/cloning, does not show the workflow popup nor redirect to the change request (#4357)
System integration
-
Fixed: Authentication to Rudder from LDAP should not require to touch WAR file (#4403)
-
Fixed: Missing property `rudder.debug.nodeconfiguration.path' in configuration file (#4542)
-
Fixed: A race condition may occur during rudder-server-root initialization (#4635)
-
Fixed: The script rudder-init.sh should not output CFEngine execution, and keep the output of all commands in the log (#4634)
Logging
-
Fixed: A developpment log line is displayed when saving Directive edit form (#4660)
Release notes
Special thanks go out to the following individuals who invested time, patience, testing, patches or bug reports to make this version of Rudder better:
-
Olivier Mauras
This version of Rudder is a final release. We have tested it thoroughly
and believe it to be free of any major bugs. However, this branch is not
marked stable'', since it still has to be proven reliable on
production systems over a period of several months. The current
stable'' release is 2.6.*.
Rudder 2.10.0~beta1 (2014-03-21)
Changes
Webapp - Config management
-
Allow exclusion and composition of groups to gain more flexibility in Nodes targeted by a Rule (#4505)
Performance and scalability
-
When generating promises, use a cache for template file (#4521)
-
Avoid useless requests and commits in SQL database (#4428)
-
Keep only the LDIF dump of the inventory when we accept/refuse it, not every time we receive a new inventory (#4560)
-
Don’t write execution report in several log files (#4520)
-
Rudder agents run times should be splayed a maximum to ensure maximum scalability (#4451)
-
allowusers is duplicated in cf-served.cf (#4444)
Techniques
-
Unix Support (#3288)
Webapp - Administration
-
Rename
change message'' feature to
change audit log'' and add more explanations (#4153)
Inventory (webapp, Fusion)
-
Support !FusionInventory version 2.3 (#4663)
System integration
-
Rename jetty and slapd init scripts and defaults files to rudder-jetty and rudder-slapd (#4510)
-
Upgrade version of jetty (7.6.14) in Rudder packages (#4477)
-
Rudder 2.10 will not support upgrades from any version older than 2.6.* (#4413)
-
Support Rudder agent on AIX 5.3+ (#4459), building less verbose (#4587), reset Epoch to 0 by default (#4563), Remove deprecated package rudder-cfengine-community (#4561)
Architecture - Refactoring
-
Ease new REST APIs creation (#4600)
Bug fixes
Performance and scalability
-
Fixed: Promise generation takes too long when getting more and more nodes (#4242)
-
Fixed: Rudder web UI freezes when too many inventory are received at the same time (#4497)
-
Fixed: Promise generation process should not lose time by forking to run ``/bin/true'' (#4475)
-
Fixed: cf-serverd looks up reverse DNS for ALL nodes at start up (#4442)
-
Fixed: Duplicated list of nodes authorized to connect to the policy server in the generated promises (#4642)
Webapp - Node management
-
Fixed: duplicated IP addresses across nodes are not accepted, preventing to handle NAT (#4429)
Techniques - System & initial promises
-
Fixed: Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from ``common'' system technique metadata (#4573)
Release notes
This software is in beta status and contains a lots of new features. We have tested it and believe it to be free of any critical bugs. The use on production systems is not encouraged at this time and is at your own risk. However, we do encourage testing, and welcome all and any feedback!