Waiting for changelog lock….
This issue might happen when the some sql statements took a very long time for execution and was accidentally aborted. Then on the next time when liquibase was to execute the same change-sets, the previous lock was held.
We can check the locks existing in database using the following query.
>select * from DATABASECHANGELOGLOCK;
The problem can be resolved by running the following query on the database.
>update DATABASECHANGELOGLOCK set locked=0, lockgranted=null, lockedby=null where id=1;