Unable to migrate MySQL database after updating to >= 2024.1

[TotallyMonica]

Steps To Reproduce

1. Set up Unified instance on <= 2023.12 utilizing a MySQL connector
2. Pull a >= 2024.1 image
3. Observe admin process crashing due to database migration issues

Expected Result

Database gets successfully migrated, with the container working successfully

Actual Result

Admin process perpetually crashes and relaunches upon unsuccessful DB migration

Screenshots or Videos

Relevant logs
docker-logs.txt
identity.log
notifications.log
api.log
admin.log

Additional Context

When working with a fresh database, this issue is not present, this appears to be exclusive to updating from a 2023.X to 2024.X installation

Githash Version

b3a6bf5-dirty

Environment Details

• Operating System: Ubuntu 22.04 (Docker host), Debian 12 (MySQL Server)
• Docker: 24.0.5
• Hardware: Linode Shared CPU 4GB

Database Image

External MariaDB 10.11.6
Known buggy versions: 2024.1-beta, 2024.2-beta
Last known working: 2023.12-beta

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[holow29]

#3651 - doesn't seem like it will be fixed.

[Greenderella]

Hi there!

Thank you for your report, it seems like it is a duplicate of #3651

You can attempt to drop the conflicting columns manually, following these steps: #3651 (comment)

This issue will now be closed.

Thanks!