Migration panics when upgrading to 1.30.0 #649

New Issue

OVERLORD · 2025-10-09T16:43:46+03:00

OVERLORD commented

2025-10-09 16:43:46 +03:00

Originally created by @PaoloAngiolillo on GitHub.

Subject of the issue

Deployment environment

vaultwarden version: 1.30.0

Install method: Kubernetes
MySQL/MariaDB or PostgreSQL version: MariaDB

Steps to reproduce

upgrade the version to 1.30.0 and start the new container.

Expected behaviour

i expect the container to start up properly with the migrations working.

Actual behaviour

the Pod is not starting because of a migration error.

Troubleshooting data

[2023-11-13 15:00:22.599][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2023-06-02-200424_create_organization_api_key", version: MigrationVersion("20230602200424") }, DatabaseError(Unknown, "Can't create table `acc_bitwarden_01`.`organization_api_key` (errno: 150 \"Foreign key constraint is incorrectly formed\")"))': src/db/mod.rs:471
   0: vaultwarden::init_logging::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys_common::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: vaultwarden::db::mysql_migrations::run_migrations
   8: vaultwarden::db::DbPool::from_config
   9: vaultwarden::main::{{closure}}
  10: rocket::async_main
  11: vaultwarden::main
  12: std::sys_common::backtrace::__rust_begin_short_backtrace
  13: std::rt::lang_start::{{closure}}
  14: std::rt::lang_start_internal
  15: main
  16: <unknown>
  17: __libc_start_main
  18: _start

Originally created by @PaoloAngiolillo on GitHub.   ### Subject of the issue  ### Deployment environment     * vaultwarden version: 1.30.0  * Install method: Kubernetes * MySQL/MariaDB or PostgreSQL version:  MariaDB ### Steps to reproduce  upgrade the version to 1.30.0 and start the new container. ### Expected behaviour  i expect the container to start up properly with the migrations working. ### Actual behaviour  the Pod is not starting because of a migration error. ### Troubleshooting data  ``` [2023-11-13 15:00:22.599][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2023-06-02-200424_create_organization_api_key", version: MigrationVersion("20230602200424") }, DatabaseError(Unknown, "Can't create table `acc_bitwarden_01`.`organization_api_key` (errno: 150 \"Foreign key constraint is incorrectly formed\")"))': src/db/mod.rs:471 0: vaultwarden::init_logging::{{closure}} 1: std::panicking::rust_panic_with_hook 2: std::panicking::begin_panic_handler::{{closure}} 3: std::sys_common::backtrace::__rust_end_short_backtrace 4: rust_begin_unwind 5: core::panicking::panic_fmt 6: core::result::unwrap_failed 7: vaultwarden::db::mysql_migrations::run_migrations 8: vaultwarden::db::DbPool::from_config 9: vaultwarden::main::{{closure}} 10: rocket::async_main 11: vaultwarden::main 12: std::sys_common::backtrace::__rust_begin_short_backtrace 13: std::rt::lang_start::{{closure}} 14: std::rt::lang_start_internal 15: main 16: <unknown> 17: __libc_start_main 18: _start ```

OVERLORD closed this issue

2025-10-09 16:43:47 +03:00

OVERLORD commented

2025-10-09 16:43:49 +03:00

@PaoloAngiolillo commented on GitHub:

Found the issue, i had to change some database collations

@PaoloAngiolillo commented on GitHub: Found the issue, i had to change some database collations

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#649