Repository navigation
Unexpected executed migrations #35626
Replies: 2 comments 1 reply
|
Hi @thomasLeclaire , Since the application seems to be working fine after the upgrade, I'd first try to understand how the migration was performed before changing anything in the database. A few questions that might help narrow this down:
The message mentioning I'd suggest checking the migration job logs and database migration history before attempting to rerun or manually modify any migrations. I've worked with application upgrades and database migrations in cloud-hosted environments, and checking the exact upgrade path usually helps avoid making a working installation worse. If you can share the upgrade sequence and relevant migration logs (with credentials or sensitive details removed), it'll be easier to narrow down what's happening. Regards, |
|
By the way, I know why there is the message it's because the migration 1.13.5 and 1.13.6 were never backported in branch 2.x of the app, cf https://github.com/open-metadata/OpenMetadata/tree/2.0.5-release/bootstrap/sql/migrations/native for example. A quick solution could be to simply backport the 2 missing folders in branches 2.x but no real ideas on the impacts. Another workaround for people like me can be to remove the 2 superfluous migrations but the same concern about impacts. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I just migrated my installation from v1.13.6 to v 2.0.5.
Used standard helm procedure and all was smooth.
From what I see, everything is working as expected, however when checking the health check in UI it says this :
Missing migrations that were not executed []. Unexpected executed migrations [1.13.5, 1.13.6]
Regards
All reactions