Actions
Bug #7849
closed
rudder-upgrade does not make some check on remote sql in case of distributed setup
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In 2.10, we introduced some modification in the database schema, which are not compatible with distributed setup
When upmerging, the commands were not updated, so they fail to correct the database schema
Updated by Nicolas CHARLES about 8 years ago
- Related to Bug #7133: Create the migration script for the database to correct the serialization of groups in the rules added
Updated by Nicolas CHARLES about 8 years ago
- Related to Bug #7161: Create a migration script for the database change for historization of global agent schedule added
Updated by Nicolas CHARLES about 8 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES about 8 years ago
- 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
Updated by Nicolas CHARLES about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|376d2513d137b54e8e7ae20d5ab0dab34cdba4b9.
Updated by Nicolas CHARLES about 8 years ago
- 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 added
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from Pending release to Released
Actions