Checksum validation fails on 4.19.1 h2 db

Liquibase Development
1

Hi, we are updating liquibase from 4.8.0 to the 4.27.0, we have some integration tests that use an h2 database. I narrowed it down to either 4.19.0 or 4.19.1 where we get the checksum issue. I am not sure if it is introduced in 4.19.0 because on this version it fails validation on this

java.io.IOException: liquibase.exception.ValidationFailedException: Validation Failed:
     116 changes have validation failures
          Cannot add a primary key column, liquibase-update-to-latest.xml::20120322-1510::wyclif
...

When upgrading to 4.19.1 the above error goes away and instead we get validation failures on the checksums

java.io.IOException: liquibase.exception.ValidationFailedException: Validation Failed:
     191 changesets check sum
          liquibase-update-to-latest.xml::0::bwolfe was: 3:ccc4741ff492cb385f44e714053920af but is now: 8:12a6014284bbf4978e29e2f37d967125
...

I see some checksum refactoring in the changelogs and cleanup but not any related breaking changes. Any ideas what changes in these versions could have caused it?

2

There were significant and breaking changes to validation and md5sum calculations that will need to be resolved. You can review the changes here:

You are making a huge jump from md5sum algorithm 3 to algorithm 8, not surprised you are running into issues:

3:ccc4741ff492cb385f44e714053920af but is now: 8:12a6014284bbf4978e29e2f37d967125

3

Thank you for your response, I didn’t see any changes to md5sum algorithm in the 4.19.0 or 4.19.1 release notes. Although the goal is to move right up to the latest version, it was in these versions that the checksums started failing. In version 4.18.0 the checksums matched, so before continuing the move to 4.27.0 I wanted to check why it would be failing on this earlier version first.