Update Alation to 2025.1

Customer Managed Applies to customer-managed instances of Alation

2025.1 Update Version Dependencies

Alation supports a direct update to version 2025.1 from the following previous versions:

  • 2024.3.3 - 2024.3.5

  • 2024.1.5 (latest minor version of 2024.1)

Note

If you are using a different minor version of 2024.3 or 2024.1, contact Alation Support to confirm whether your update path is supported and to get recommendations.

The information about new features and bug fixes in 2025.1 is available in Release Notes 2025.1 (General Availability).

Update from Version 2023.3.x or Older

Direct update to version 2025.1 is not supported from 2023.3.x or older versions. First, update Alation to a version that supports the update to 2025.1 and then perform a second update to 2025.1.

Update Known Issues

Reset Postgres Password

If you have a password set on the internal PostgreSQL database (Rosemeta), the update will result in an error similar to the following:

WARN: unable to check pg-1: [DbConnectError] unable to connect to 'dbname='postgres' port=5432':
FATAL: password authentication failed for user "postgres"
password retrieved from file "/home/postgres/.pgpass"
ERROR: [056]: unable to find primary cluster - cannot proceed

The update process requires that the password on the internal PostgreSQL database should be cleared for the time of the update. The password can be set again after the update is completed. On how to set the Postgres password, see Set Password for Internal PostgreSQL Instances.

Update-Specific Information

The patch release 2024.3.4.2 included an upgrade of the Alation internal PostgreSQL database and the Alation Analytics PostgreSQL database to the next minor version 16.5.

If you are updating from a minor version where the PostgreSQL 16.5 upgrade has not yet occurred, it will automatically happen during the update to 2025.1.

Update Steps

Step 1: Scan Postgres

We recommend using the scan_postgres action to validate that the internal Postgres database is in a healthy state before the update. For steps, see How to Scan Postgres for Corrupted Indexes.

Note

If in your instance the Postgres scan runs on a schedule, you can check the scan-postgres.log file in /opt/alation/site/logs inside the Alation shell to check the Postgres state.

Step 2: Verify Backup Availability

Ensure you have a valid, up-to-date Alation backup. We recommend taking the most recent backup possible to closely match your current data.

Step 3: Update the Alation Application

Step 4: Update Alation Connector Manager

This step applies if you are using Open Connector Framework (OCF) and OCF connectors.

Update Alation Connector Manager using the steps in Update Alation Connector Manager.

Step 5: Update Alation Analytics

This step applies if you are using the Alation Analytics application.

Use the steps in Update Alation Analytics V2 to update the Alation Analytics application.