Bug #7849 closed
rudder-upgrade does not make some check on remote sql in case of distributed setup
Added by Nicolas CHARLES over 10 years ago.
Updated about 10 years ago.
Description
In 2.10, we introduced some modification in the database schema, which are not compatible with distributed setup
Related to Bug #7133 : Create the migration script for the database to correct the serialization of groups in the rules
Related to Bug #7161 : Create a migration script for the database change for historization of global agent schedule
Status changed from New to In progress
Status changed from In progress to Pending technical review Assignee changed from Nicolas CHARLES to Benoît PECCATTE Pull Request set to https://github.com/Normation/rudder-packages/pull/878
Status changed from Pending technical review to Pending release % Done changed from 0 to 100
Related to Bug #7850 : Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP
Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.
Also available in: PDF Atom
Updated by 
Updated by