Bug #9749
closed
rudder-upgrade should use the database name from the webapp configuration
Added by Alexis Mousset almost 8 years ago.
Updated almost 8 years ago.
Category:
System integration
Description
Currently it uses the hardcoded "rudder" name which breaks upgrade when the database name is different.
- Subject changed from rudder-upgrade should use the database name from teh webapp configuration to rudder-upgrade should use the database name from the webapp configuration
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1147
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Category changed from Packaging to System integration
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.1, 3.1.16 and 3.2.10 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by