Migration from any 5.0 minor version is supported (see below for migration from older versions).
The Rudder packages ncf, ncf-api-virtualenv, rudder-inventory-endpoint, rudder-inventory-ldap, rudder-jetty and rudder-techniques have been merged into rudder-webapp. This means that on a server upgrade from Rudder 5.0 those packages will all be removed.
This is normal!
The technique tools folder (in
The folder is left in place, but not automatically shared anymore.
If you relied on the tools copy mechanism to share files, you can replace it by a standard recursive copy from the shared files.
Rudder generic method
Before the 6.0 Rudder version, when in audit policy mode, the method was not executing the command passed in parameters and would always report an error.
In order to limit the compliance drift when switching policy mode we chose to make the method behave in the exact same way in audit mode than in enforce mode because:
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:
Direct upgrades from 4.3.x and older are no longer supported on 6.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 6.0.
Rudder agent 4.3 and 5.0 are fully compatible with Rudder server 6.0. It is therefore not strictly necessary to update all your agents to 6.0.
These agents are not compatible with Rudder 6.0, and you have to upgrade them. Be careful to follow the upgrade path explained above.
← on SLES on Debian/Ubuntu →