Project

General

Profile

Actions

Defect #43699

open

Fatal error during database migration process

Added by Tim Totten about 6 hours ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

So a few years back (2019) we switched from building Redmine from source to using the official Docker image.
Which has worked great since then and made upgrades so much easier.

Until today. The first time I've had to rollback an upgrade!

The image I was upgrading from (and have since rolled back to):

Environment:
  Redmine version                6.0.6.stable
  Ruby version                   3.3.8-p144 (2025-04-09) [x86_64-linux]
  Rails version                  7.2.2.1
  Environment                    production
  Database adapter               Mysql2
  Mailer queue                   ActiveJob::QueueAdapters::AsyncAdapter
  Mailer delivery                smtp
Redmine settings:
  Redmine theme                  Default
SCM:
  Subversion                     1.14.2
  Mercurial                      6.3.2
  Bazaar                         3.3.2
  Git                            2.39.5
  Filesystem                     
Redmine plugins:
  no plugin installed

The image I was upgrading to was using tag `redmine:latest`, and is identified as version `6.1.1` in the image metadata.

It complained first about not being able to rename `oauth_access_grants`.
A second try after tweaking the running MariaDB instance had an error about `oauth_applications` already existing.
So I dropped both those tables and tried a third time. The original error about renaming the (now non-existent) table re-appeared.

So I ended up restoring my database and rolling back to 6.0.6 which works fine. I'm sticking with it until I can find a working solution.

I am attaching the combined logs from the 6.1.1 container to see if they make any more sense to a Redmine developer.


Files

No data to display

Actions

Also available in: Atom PDF