...

Make sure to follow Preparing for Upgrade before applying the upgrade.

...

Install Additional Packages

...

Version 1.0.22.0 includes new features that are based on additional packages that need to be installed on the operating system before applying the upgrade.

• For DPOD Appliance Mode users

...

• :
  

...

• Please follow now the instructions documented in the Special Step 1 page.

• For DPOD Non-Appliance Mode users:

  • Make sure the following packages (RPMs) are installed and up-to-date from the official Red Hat/Rocky Linux repositories:
    bc, chrony, cjose, curl, fontconfig, hiredis, httpd, initscripts, jansson, lz4, mailcap, mod_ssl, nmon, numactl, policycoreutils-python-utils, tuned, unzip, wget, xmlstarlet.

  • Note: The EPEL repository (e.g.: dnf install epel-release) may be required to install the packages hiredis and nmon.

  • The installation is usually performed by executing dnf:

    Code Block
    dnf install bc chrony cjose curl fontconfig hiredis httpd initscripts jansson lz4 mailcap mod_ssl nmon numactl policycoreutils-python-utils tuned unzip wget xmlstarlet

  • If the command fails to find the packages, you may manually download the RPM files and install them.

Obtain the Software Upgrade

...

• Execute the following commands:
  Note: Starting from DPOD 1.0.22.0, it is possible to use a user with sudo permissions instead of running the upgrade by the root user itself.

  Code Block
  mkdir -p /installs/backups cd <CEF_DIRECTORY> chmod 755 <CEF_FILE> sudo ./<CEF_FILE>

• By default, the installation will extract temporary files to /app/tmp directory. To change the destination directory, use the option --staging-path <directory>.

• Do not interrupt the software update process after it has started.
  If SSH connection is lost during upgrade, the upgrade will still continue. Reconnect to the server and check the log files for the process status and outcome.

• Note: Once the upgrade to 1.0.22.0 is completed, DPOD no longer requires the root user for performing administrative tasks via the server CLI (e.g.: using SSH).
  Most of the administration of DPOD should be performed with the non-administrative user that is also running the DPOD services (usually dpodsvc or storeadm), such as starting/stopping services, configuring LDAP, export/import, etc. These tasks can also be accomplished from the Admin Console.
  However, since DPOD also configures the operating system (the httpd service, OS limits, firewall rules, services in /etc/init.d, etc.), some actions require sudo, such as the installation, upgrading DPOD, backup, restore and generating a mustgather file.

• Note: Once the upgrade to 1.0.22.0 is completed, CLI commands need to be executed with their full path.
  e.g.: Use /app/scripts/app-utils.sh instead of app-util.sh.

...

Upgrade OS of DPOD Appliance Mode

It is required to migrate the operating system from CentOS to Rocky Linux after applying the upgrade. Please follow now the instructions documented in the Special Step 2 page.

Restore Certificates of Web & Admin Consoles

...

Note
This section should be applied after upgrading from 1.0.21.0 to 1.0.22.0

...

.

Due to a bug in the upgrade process of version 1.0.22.0, the configuration of custom certificates for the Web Console and Admin Console (see Replacing Certificates of Web & Admin Consoles) is lost during the upgrade.

If custom certificates have been configured before the upgrade, please , you may re-configure them using the same procedure, or alternatively follow the steps below to restore that configuration:

...