Hello Liquibase Family,
We’ve been conducting several Liquibase deployments and observed that some change sets are not executing. The issue appears to be related to the MD5 checksum calculation, or possibly a NULL value being inserted into the DATABASECHANGELOG table. Has anyone else encountered this issue?
Pete
August 1, 2025, 4:17pm
2
Hi @kahumphrey and welcome to the forum! To help figure out what’s going on can you tell me more about your environment and recent activity? Specifically:
Version of Liquibase
Whether or not you have updated Liquibase to a new version recently
Log or console output that demonstrates the issues you’re seeing
Affected rows in the DATABASECHANGELOG table
We have had a user report a recent issue with checksums in our GitHub repo. Maybe this is similar to the issue you’re seeing?
opened 09:52AM - 10 Jul 25 UTC
closed 08:38PM - 16 Jul 25 UTC
TypeBug
checksum
### Search first
- [x] I searched and no similar issues were found
### Descrip… tion
After upgrade of the:
org.liquibase:liquibase-core:4.32.0 to 4.33.0
and deployment of the component
One out of multiple changelog checksum comparison fails.
Stack trace is the following:
`Caused by: liquibase.exception.ValidationFailedException: Validation Failed:
1 changesets check sum
db/changelog/0043-MC-1863-add-last-transaction-date-to-store.xml::MC-1863-add-last-transaction-date-to-store::AUTHOR_CONTENT_REMOVED was: 9:fbdda523ad45125582c831e6da93d685 but is now: 9:ada99b6add4b9b0b00f4e5988ce369bf
at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:386)
at liquibase.command.core.helpers.DatabaseChangelogCommandStep.run(DatabaseChangelogCommandStep.java:89)
at liquibase.command.CommandScope.lambda$execute$6(CommandScope.java:263)`
The changelog file content is the following (author removed):
`<?xml version="1.1" encoding="UTF-8" standalone="no"?>
<databaseChangeLog
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.7.xsd"
logicalFilePath="db/changelog/0043-MC-1863-add-last-transaction-date-to-store.xml">
<changeSet id="MC-1863-add-last-transaction-date-to-store" author="AUTHOR_CONTENT_REMOVED">
<addColumn tableName="store">
<column name="last_transaction_date" type="DATE" valueDate="DATE_SUB(CURRENT_DATE(), INTERVAL 27 DAY)"/>
</addColumn>
</changeSet>
</databaseChangeLog>`
The changelog was executed way back and holds following entry in the DATABASECHANGELOG table:
`"id","author","filename","dateExecuted","orderExecuted","execType","md5sum","description","comments","tag","liquibase","contexts","labels","deployment_id"
MC-1863-add-last-transaction-date-to-store,AUTHOR_CONTENT_REMOVED,db/changelog/0043-MC-1863-add-last-transaction-date-to-store.xml,2023-04-03 13:54:29.848,76,EXECUTED,"9:fbdda523ad45125582c831e6da93d685",addColumn tableName=store,"",,"4.17.2",,,"0522851965"
`
There are no more problems notified with any of the other changelogs compared or executed in this or the other application components.
Under a local run , it was confirmed under a DEBUG the difference in the checksum being generated:
4.33 run:
<img width="1763" height="1007" alt="Image" src="https://github.com/user-attachments/assets/3343a4e4-c519-4a9a-92fc-2c3e0b8889eb" />
4.32 run:
<img width="1763" height="1007" alt="Image" src="https://github.com/user-attachments/assets/774e8ad6-d89a-42ae-9d96-00ffc71da443" />
### Steps To Reproduce
explained in the description
### Expected/Desired Behavior
Upgrade of the liquibase-core should not result in rejection of valid and executed changelogs.
### Liquibase Version
4.33.0
### Database Vendor & Version
Google Cloud Spanner
### Liquibase Integration
spring boot
### Liquibase Extensions
liquibase-spanner
### OS and/or Infrastructure Type/Provider
GCP
### Additional Context
org.springframework.boot" version "3.4.5"
com.google.cloud:spring-cloud-gcp-dependencies:6.1.1
com.google.cloudspannerecosystem:liquibase-spanner:4.31.1
org.liquibase:liquibase-core:4.33.0
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR (Thank you!)
