Message regarding an empty result set for databasechangeloglock (in 3.0.2 but not in 3.0.0)

Scenario With No Such Error:

  • Run with liquibase.integration.spring.SpringLiquibase
  • Executed against mysql database

Any reason why the older version is more stable than the newer one?

I created to track the issue. I haven’t gotten a chance to see what caused the regression yet.