Error on startup in cosmos DB with mongo 4.2 API

[millymanca]

Here my configs:
Cosmos DB on Azure with mongo 4.2 driver
Quarkus Java 11
Dependencies:

<dependency>
        <groupId>org.liquibase</groupId>
        <artifactId>liquibase-core</artifactId>
        <version>4.9.0</version>
     </dependency>

     <dependency>
        <groupId>org.liquibase.ext</groupId>
        <artifactId>liquibase-mongodb</artifactId>
        <version>4.9.0</version>
     </dependency>

2022-04-13 16:38:43,777 INFO [liq.ext] (Quarkus Main Thread) Successfully Acquired Change Log Lock
2022-04-13 16:38:44,204 INFO [liq.ext] (Quarkus Main Thread) Create Database Change Log Collection
2022-04-13 16:38:44,205 INFO [liq.ext] (Quarkus Main Thread) Creating database history collection with name: profiler.DATABASECHANGELOG
2022-04-13 16:38:46,435 INFO [liq.ext] (Quarkus Main Thread) Created database history collection : profiler.DATABASECHANGELOG
2022-04-13 16:38:46,435 INFO [liq.ext] (Quarkus Main Thread) Adjusting database history Collection with name: profiler.DATABASECHANGELOG
2022-04-13 16:38:46,436 INFO [liq.ext] (Quarkus Main Thread) Adjusted database history Collection with name: profiler.DATABASECHANGELOG
2022-04-13 16:38:46,772 INFO [liq.ext] (Quarkus Main Thread) Release Database Lock
2022-04-13 16:38:46,819 INFO [liq.ext] (Quarkus Main Thread) Successfully released change log lock
2022-04-13 16:38:46,819 SEVERE [liquibase] (Quarkus Main Thread) Could not release lock: liquibase.exception.LockException: liquibase.exception.LockException: Did not update change log lock correctly.

0 rows were updated instead of the expected 1 row there are more than one rows in the table
at liquibase.nosql.lockservice.AbstractNoSqlLockService.releaseLock(AbstractNoSqlLockService.java:215)

Anyone has this problem?