Hi, we upgraded liquibase from 3.8.9 to 4.3.5.
We faced problems with checksums not matching, we fixed it with spring.liquibase.clear-checksums=true in application.properties (spring boot). However now md5sum column in databsechangelog table contains only nulls for the changes that originated from the older version.
When I run application with liquibase DEBUG logging I can see that new checksums are calculated for the old records, however they are not updated:
{"timestamp":"2021-12-14T09:15:59.928+01:00","level":"DEBUG","thread":"main","context":"default","message":"Updating null or out of date checksum on changeSet db/changelog/7.10-changelog.xml::7.10/postgres_identity_7.10.0::x@x.com to correct value","source":"liquibase.changelog","service_domain":"service-order-service-inventory","environment_name":"-","application_name":"TAN-Orchestrator"}
{"timestamp":"2021-12-14T09:15:59.928+01:00","level":"DEBUG","thread":"main","context":"default","message":"Executing with the 'jdbc' executor","source":"liquibase.executor","service_domain":"service-order-service-inventory","environment_name":"-","application_name":"TAN-Orchestrator"}
{"timestamp":"2021-12-14T09:15:59.929+01:00","level":"DEBUG","thread":"main","context":"default","message":"Computed checksum for inputStream as cee1316ba2a7c7259256dadfa78c5582","source":"liquibase.util","service_domain":"service-order-service-inventory","environment_name":"-","application_name":"TAN-Orchestrator"}
{"timestamp":"2021-12-14T09:15:59.929+01:00","level":"DEBUG","thread":"main","context":"default","message":"Computed checksum for 8:cee1316ba2a7c7259256dadfa78c5582: as 06ab54719b4fd90eaee95564e8ae1836","source":"liquibase.util","service_domain":"service-order-service-inventory","environment_name":"-","application_name":"TAN-Orchestrator"}
{"timestamp":"2021-12-14T09:15:59.930+01:00","level":"DEBUG","thread":"main","context":"default","message":"0 row(s) affected","source":"liquibase.executor","service_domain":"service-order-service-inventory","environment_name":"-","application_name":"TAN-Orchestrator"}
How can we fix this problem? Hopefully there is other solution than to update it manually, we face this issue on multiple microservices.
Thank you