Migration from any 5.0 minor version is supported (see below for migration from older versions).
Rudder 5.0.9 changes the default log level for the configuration server in Rudder.
This allows easier debugging and tracability of policy updates, so we enabled it by default, but will produce more logs. If you want to revert to the previous behavior (which only logs errors):
# You need to uncomment and let empty CFENGINE_COMMUNITY_PARAMS_1=""
Verbosity options can be:
Migration from 4.1, 4.2 or 4.3 are supported, so you can upgrade directly to 5.0.
The following features are now provided as plugins and no more available as part of default Rudder installation starting from 5.0:
If you were using them, upgrade will disable them and you will have to install the plugin. Read the plugins page on our website for more information.
On RHEL/centOS and SLES systems, when upgrading from a 4.1 older than 4.1.13, a 4.2 older
than 4.2.7 or a 4.3 older than 4.3.3,
it is necessary to explicitely upgrade
This has been fixed in the packages, but the problem is caused by the package in the version your are upgrading from.
If your Rudder server was upgraded from a 4.1 or older installation on Ubuntu 12.04 LTS or 14.04 LTS, you may still be using port 5514 for syslog communication with nodes.
It not necessary anymore, you can switch back to the default
by changing the port in the
Direct upgrades from 4.0.x and older are no longer supported on 5.0. If you are still running one of those, either on servers or nodes, please first upgrade to one of the supported versions, and then upgrade to 5.0.
Rudder agent 4.1, 4.2 and 4.3 are fully compatible with Rudder server 5.0. It is therefore not strictly necessary to update all your agents to 5.0.
These agents are not compatible with Rudder 5.0, and you have to upgrade them. Be careful to follow the upgrade path explained above.
← on SLES on Debian/Ubuntu →