Project

General

Profile

Bug #9749

rudder-upgrade should use the database name from the webapp configuration

Added by Alexis MOUSSET about 1 year ago. Updated 12 months ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

Currently it uses the hardcoded "rudder" name which breaks upgrade when the database name is different.


Subtasks

Bug #9765: rudder-upgrade should use the database name from the webapp configuration - 4.0 branchReleasedNicolas CHARLES

Associated revisions

Revision ddc235da
Added by Alexis MOUSSET about 1 year ago

Fixes #9749: rudder-upgrade should use the database name from the webapp configuration

History

#1 Updated by Alexis MOUSSET about 1 year ago

  • 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

#2 Updated by Alexis MOUSSET about 1 year ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#3 Updated by Alexis MOUSSET about 1 year ago

  • 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

#4 Updated by Alexis MOUSSET about 1 year ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

#5 Updated by Alexis MOUSSET about 1 year ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#6 Updated by Vincent MEMBRÉ 12 months ago

  • Category changed from Packaging to System integration

#7 Updated by Vincent MEMBRÉ 12 months ago

  • 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