Docker container fails with migration lock

Few details.
everything was fine till last week. due to some reasons we removed /deleted the pod and moved to another Aks.
DB is Postgress.
Now the pod is not up due to un run migrations.

logs:
2022-03-08 18:38:02,209 INFO plugins.dependencies :: Metabase Oracle Driver dependency {:class oracle.jdbc.OracleDriver} satisfied? false

2022-03-08 18:38:02,210 INFO plugins.dependencies :: Plugins with unsatisfied deps: ["Metabase Vertica Driver" "Metabase Oracle Driver"]

2022-03-08 18:38:02,211 INFO metabase.core :: Setting up and migrating Metabase DB. Please sit tight, this may take a minute...

2022-03-08 18:38:02,216 INFO db.setup :: Verifying postgres Database Connection ...

2022-03-08 18:38:03,442 INFO db.setup :: Successfully verified PostgreSQL 10.17 application database connection. :white_check_mark:

2022-03-08 18:38:03,443 INFO db.setup :: Running Database Migrations...

2022-03-08 18:38:03,919 INFO db.setup :: Setting up Liquibase...

2022-03-08 18:38:04,182 INFO db.setup :: Liquibase is ready.

2022-03-08 18:38:04,183 INFO db.liquibase :: Checking if Database has unrun migrations...

2022-03-08 18:38:06,841 INFO db.liquibase :: Database has unrun migrations. Waiting for migration lock to be cleared...

2022-03-08 18:38:08,848 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364@3293288e: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

2022-03-08 18:38:10,852 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364@3293288e: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

2022-03-08 18:38:12,856 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364@3293288e: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

2022-03-08 18:38:14,861 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364@3293288e: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

2022-03-08 18:38:16,864 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364@3293288e: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

2022-03-08 18:38:18,873 ERROR metabase.core :: Metabase Initialization FAILED

liquibase.exception.LockException: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

at metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__14364.invoke(liquibase.clj:109)

Hi @gopalappu
Make sure you have backups. Go to the Postgres database table databasechangeloglock and truncate it or unlock the row and start Metabase again.
Make sure you're only starting a single pod during upgrades.