Project

General

Profile

Actions

Bug #4309

closed

Rudder webapp hangs on xml migration if upgrading from 2.6/2.4

Added by Vincent MEMBRÉ about 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
1
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Rudder cannot be upgraded from 2.4/2.6 to 2.9.0.

When rudder webapp starts after upgrade, the xml migration process is repeated indefinetely, and rudder web interface will not work.

Those lines are repeated indefinetely in Rudder webapp:

[2014-01-02 11:26:49] INFO  migration - Older migration completed, relaunch migration
[2014-01-02 11:26:49] INFO  migration - Found and older migration to do
[2014-01-02 11:26:49] INFO  migration - Older migration completed, relaunch migration
[2014-01-02 11:26:49] INFO  migration - Found and older migration to do
[2014-01-02 11:26:49] INFO  migration - Older migration completed, relaunch migration
[2014-01-02 11:26:49] INFO  migration - Found and older migration to do

This is because rudder webapp does not complete migration from fileformat 3 to 4 before upgrade

Actions #1

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/408
Actions #2

Updated by Vincent MEMBRÉ about 10 years ago

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

Updated by Anonymous about 10 years ago

Actions #4

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.9.1, which was released today.
Check out:

Actions

Also available in: Atom PDF