Installation and upgrades

Startup logs wait for changelog lock

The service keeps logging Waiting for changelog lock... or fails with Could not acquire change log lock. This happens when the database holds a stale Liquibase lock from an interrupted startup or shutdown.

Stop the Allure TestOps service.
Connect to the testops database:
```
psql -h 127.0.0.1 -U testops testops
```
Check the lock state:
```
SELECT * FROM databasechangeloglock;
```

Clear the stale lock:

UPDATE databasechangeloglock SET locked=FALSE, lockgranted=NULL, lockedby=NULL WHERE id=1;

Start the service.

Upgrade fails with `syntax error at or near "nulls"`

Startup logs show a Liquibase failure with syntax error at or near "nulls". This means PostgreSQL is below version 15, which is the minimum required for version-5 upgrade paths.

Check the database version:

SELECT version();

Fix:

If you already attempted the upgrade, restore the database from backup first.
Upgrade PostgreSQL to version 15 or newer.
Repeat the TestOps upgrade.

Integrations fail with `unable to invoke cipher due to bad padding`

This usually means the encryption password for stored secrets was not carried forward during migration or redeployment.

Check these first:

the original value of ALLURE_CRYPTO_PASSWORD, TESTOPS_CRYPTO_PASSWORD, or cryptoPass, depending on deployment type;
accidental whitespace or other changes in the copied value.

Fix: restore the original crypto-password value in the new deployment configuration.

If the original value cannot be recovered, re-enter the affected integration credentials after the instance is running with the new crypto password.