Upgrade

This page provides information on special requirements or deviations from the normal SD Elements upgrade procedure when using sde-admin as your upgrade tool. For containerized upgrade notes, please look here.

SD Elements 2022.4

Pre-Upgrade Steps

Below are the changes an administrator of SD Elements should verify before attempting an upgrade to version 2022.4.

  • Ensure sde-admin is version 2.2.8 or higher. See instructions below.

  • If you are upgrading from a release older than 2022.3 (2022.2 or 5.x), please review the 2022.3 upgrade notes and be aware of those changes.

  • If you are on RHEL7 confirm your subscription status using sudo subscription-manager status. If you see any status besides current, please contact support@sdelements.com.

SD Elements 2022.3

Summary

Starting with 2022.3, systems will be upgraded automatically to Postgres 12.x during an SD Elements upgrade.

  • The PostgreSQL upgrade tool copies the entire database (and all SD Elements database instances) from a PostgreSQL 9 data directory to a PostgresSQL 12 data directory.

  • The SD Elements upgrade process will take longer than normal due to this database migration. Plan accordingly.

  • If you maintain a custom encryption configuration for Postgres, please contact support before you start your upgrade.

Pre-Upgrade Steps

Below are the changes an administrator of SD Elements should verify before attempting an upgrade to version 2022.3.

  • [IMPORTANT] Refresh upstream yum repository configuration by running sudo subscription-manager refresh from the command line.

  • Ensure unused SD Elements versions are removed using sde manage_releases as this will recover disk space and reduce overall upgrade time.

  • Ensure there is sufficient disk space to hold a copy of your Postgres data by running sudo du -sh /var/lib/pgsql/ and comparing that to available space using df -h.

  • Ensure a complete backup is created using sde backup create from the command line.

  • Ensure sde-admin is version 2.2.8 or higher. See instructions below.

sde-admin 2.2.8

Install/upgrade by running the following commands as root user:

user="$(grep -Po "(?<=^repo_user = )(.*)" /docs/sde/updater.cfg)"
encrypted_pass="$(grep -Po "(?<=repo_pass =\K) (.*)" /docs/sde/updater.cfg)"
fernet_key="$(cat /etc/sde/.encryption_key | base64 --decode)"
pass="$(python3.6 -c "import cryptography.fernet; print(cryptography.fernet.Fernet('${fernet_key}').decrypt('${encrypted_pass}'.encode()).decode())")"
umask 0002 && pip install --upgrade --force-reinstall sde-admin==2.2.8 --index="https://${user}:${pass}@pypi.sdelements.com/pulp/python/web/prod/simple/"

results matching ""

    No results matching ""