Troubleshooting Upgrade Issues from Allure TestOps ver 4 to 5 and 5 to 5, incorrect version of PostgreSQL

Modified on Fri, 11 Apr at 6:46 PM

Troubleshooting Upgrade Issues from Allure TestOps ver 4 to Allure TestOps ver 5

Issue Description

When upgrading from Allure TestOps version 4 to version 5, you might encounter log errors during startup indicating issues with the underlying database. These errors typically mean that there is at least one unsatisfied condition necessary for the upgrade, specifically related to the version of PostgreSQL.

Common Error

Upon starting the upgraded version, if your system logs display errors similar to the following, it suggests that your PostgreSQL version is below the required version 15.

Example of a Log Error

Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name <something> Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name ‘liquibase’ defined in class path resource <something> Migration failed for changeset <something>
Reason: liquibase.exception.DatabaseException: ERROR: syntax error at or near “nulls”
<something>
Failed SQL: (0) create unique index if not exists <something>  nulls not distinct

important markers of this issue:

syntax error at or near “nulls”
cancelling refresh attempt
Unsatisfied dependency expressed through constructor
Failed SQL: (0) create unique index if not exists

If you observe such markers as ones provided above, then you haven'd had upgraded your PostgreSQL server to version 15.

The log indicates a **syntax error at or near "nulls"** which is typically a feature not supported in PostgreSQL versions below 15.

The error pertains to a failure in executing a Liquibase changeset, which tries to use SQL syntax that is incompatible with your PostgreSQL version.

Solution

The upgrade of the PostgreSQL server to the version 15 is a mandatory part of the migration to version 5 and it cannot be completed until such upgrade has been completed.

Verify PostgreSQL Version

Check the current version of PostgreSQL running with your Allure TestOps installation. You can do this by connecting to your PostgreSQL database and running the query:

SELECT version();

Upgrade PostgreSQL

If your PostgreSQL version is below 15, you need to upgrade it to at least version 15 to meet the requirements of Allure TestOps ver 5.

Follow the upgrade instructions provided in the PostgreSQL official documentation or consult with your database administrator.