Migration Error from 0.49.8 to 0.49.9 or 0.49.10 about metabase

[paoliniluis]

no, this is another thing, not the one that we already fixed

[ZencareJake]

Similar failure here:

Reason: clojure.lang.ExceptionInfo: Unexpected character ('T' (code 84)): Expected space separating root-level values
liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v49.2024-04-09T10:00:03::qnkhuat:
2024-05-15 20:22:22,225 ERROR metabase.core :: Metabase Initialization FAILED
... 236 more
at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 3]
Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('T' (code 84)): Expected space separating root-level values

It looks like @ppavlov39 is having similar issues here

In the logs I've listed above, the commit in question can be seen here

[ZencareJake]

Looks like this has been addressed in some closed issues and will be resolved in 49.11

#42659 (comment)

[ZencareJake]

no, this is another thing, not the one that we already fixed

Gotcha, my apologies.

[qnkhuat]

An old thread on this: https://metaboat.slack.com/archives/C064EB1UE5P/p1704840138989869

[qnkhuat]

@jeromedumas-peekin I need some info to debug this.

Could you give us a dump of your databasechangelog table?

select * from databasechangelog;

[tomahawk-pilot]

got this error after new update.

May 16, 2024 at 11:21 (UTC+5:30)	liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v49.2024-04-09T10:00:03::qnkhuat:	[78c11c62d9c145849baa3ee103273639](https://ap-south-1.console.aws.amazon.com/ecs/v2/clusters/eximpe-production-ap-south-1/services/metabase/tasks/78c11c62d9c145849baa3ee103273639?region=ap-south-1)	metabase
May 16, 2024 at 11:21 (UTC+5:30)	Reason: clojure.lang.ExceptionInfo: Unrecognized token 'nTmBnuuIywXxYSR': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')```


i had to take a db snapshot and downgrade to v0.49.7 for the metabase to come back up. 

[jeromedumas-peekin]

@jeromedumas-peekin I need some info to debug this.

Could you give us a dump of your databasechangelog table?

select * from databasechangelog;

Yes, please find dump of databasechangelog table.
databasechangelog.csv

[jeromedumas-peekin]

Same error with version 0.49.11

[qnkhuat]

@jeromedumas-peekin, I am looking at your database change log, and it seems like there was a weird migration sequence. 2 problems:

1. There are 2 migrations with IDs v00.00-000, and we should only have one.

2. all databasechangelog.filename are migrations/000_migrations.yaml except for one entry.

This filename only existed in the pre-48 versions; from 48, we changed it to either migrations/000_legacy_migrations.yaml or migrations/001_update_migrations.yaml.

This suggests that there was some attempt to run a pre48 version recently without a proper downgrade.

[qnkhuat]

The problem we're having here is not with migration, but it's trying to run this query on startup

UPDATE databasechangelog
SET FILENAME = CASE
                   WHEN ID = v00.00-000 THEN migrations/001_update_migrations.yaml
                   WHEN ID < v45.00-001 THEN migrations/000_legacy_migrations.yaml
                   ELSE migrations/001_update_migrations.yaml
               END

and it fails because your database change log has 2 migrations with id v00.00-000

[qnkhuat]

Try this and see if it resolves your issue.

[jeromedumas-peekin]

Solved with delete from databasechangelog where id = 'v00.00-000' and author = 'qnkhuat' and filename = '001_update_migrations.yaml';

[qnkhuat]

@jeromedumas-peekin for our information, did something weird happen with your migration sequence?

I want to know why you have 2 such migrations in the first place.

[jeromedumas-peekin]

@qnkhuat No, nothing unusual happened with the migration sequence. I don't understand why i have 2 such migrations.