The Dex service startup fails during the migration phase due to column addition conflicts, and the conflicting columns are random each time.

[hzm199822]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.
• I am not looking for support or already pursued the available support channels without success.

Version

2.40

Storage Type

MySQL

Installation Type

Custom container image

Expected Behavior

Dex is deployed in a Kubernetes pod and connects to the MySQL database through a Kubernetes service.

Actual Behavior

The migration occasionally fails during the Dex startup process.

mysql
The migration table normally has 12 columns, but when the migration fails, it only has 8 or 9, always missing a few columns. This is likely a result of the migration failure, where not all of the migration steps are successfully applied, leading to incomplete changes in the database schema.

Steps To Reproduce

No response

Additional Information

No response

Configuration

No response

Logs

No response

[nabokihms]

@hzm199822 could you please provide more info about your MySQL setup? We were in the process of migrating to another migration engine, maybe it will help, but I want to try reproducing the error first.