Project

General

Profile

Actions

Bug #9749

closed

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

Added by Alexis Mousset about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

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


Subtasks 1 (0 open1 closed)

Bug #9765: rudder-upgrade should use the database name from the webapp configuration - 4.0 branchReleasedNicolas CHARLES2016-12-02Actions
Actions #1

Updated by Alexis Mousset about 8 years 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
Actions #2

Updated by Alexis Mousset about 8 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #3

Updated by Alexis Mousset about 8 years 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
Actions #4

Updated by Alexis Mousset about 8 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
Actions #5

Updated by Alexis Mousset about 8 years ago

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

Updated by Vincent MEMBRÉ about 8 years ago

  • Category changed from Packaging to System integration
Actions #7

Updated by Vincent MEMBRÉ about 8 years 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.

Actions

Also available in: Atom PDF