Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

Article Number: 000198690

Security Vulnerability CVE-2022-0778 Detected Against OpenSSL in PowerPath Management Appliance Versions 3.0.x, 3.1, and 3.2.x

Summary: Security vulnerability CVE-2022-0778 detected against OpenSSL in PowerPath Management Appliance (PPMA) versions 3.0.x, 3.1, and 3.2.x

Article Content

Security Article Type

Security KB

CVE Identifier

CVE-2022-0778

Issue Summary

Security vulnerability detected against OpenSSL in PowerPath Management Appliance (PPMA) versions 3.0.x, 3.1, and 3.x

The following OpenSSL versions have been detected as vulnerable.

  • PPMA versions 3.0 and 3.0 P01:

Libopenssl-devel-1.0.2j-60.60.1
Openssl-1.0.2j-60.60.1
Libopenssl1_0_0-1.0.2j-60.60.1

  • PPMA versions 3.1, 3.2 P01, and 3.2 SP1:

Openssl-1_0_0-1.0.2p-3.14.1
Libopenssl-1_0_0-devel-1.0.2p-3.14.1
Libopenssl1_0_0-1.0.2p-3.14.1

Details

Upgrading OpenSSL in PowerPath Management Appliance 3.x

About this task
Upgrade of OpenSSL packages in PowerPath Management Appliance version 3.1 or 3.2 using the upgrade .zip file. You must have root privileges to carry out the upgrade.

Prerequisites:
Download the Powerpath-Openssl_Patch_OVA_VHD_3.1_3.2.zip from the attachments of this KB. This .zip file contains the latest OpenSSL packages.

Steps to upgrade PPMA 3.1, 3.2, 3.2 P01, 3.2 SP1 OVA, or VMware Hyper-V (VHD)

  1. SSH into the PowerPath Management Appliance

  2. Download the "Powerpath-Openssl_Patch_OVA_VHD_3.1_3.2.zip" file to a known folder location on PPMA

  3. Change to the directory in which the downloaded .zip file is copied.

cd <upgrade_package_directory>

  1. Extract the .zip file contents.

unzip Powerpath-Openssl_Patch_OVA_VHD_3.1_3.2.zip

  1. PowerpathChange to the -Openssl_Patch_OVA_VHD folder

cd Powerpath-Openssl_Patch_OVA_VHD_3.1_3.2

  1. Stop OpenSSL, Tomcat, Apache, and Data Collector services using systemctl commands

systemctl stop sshd.service
systemctl stop tomcat
systemctl stop apache2
systemctl stop datacollector

  1. Upgrade the OpenSSL packages using RPM command

rpm -Uvh --nosignature  libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm

Example:
==============================================================================
# rpm -Uvh --nosignature libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm

Preparing...                     ################################# [100%]
Updating / installing...
 1:libopenssl1_0_0-1.0.2p-3.48.2 ################################# [ 17%]
 2:libopenssl-1_0_0-devel-1.0.2p-3.4############################## [ 33%]
 3:openssl-1_0_0-1.0.2p-3.48.2    ################################ [ 50%]
Cleaning up / removing...
   4:openssl-1_0_0-1.0.2p-3.14.1  ################################# [ 67%]
   5:libopenssl-1_0_0-devel-1.0.2p-3.1############################# [ 83%]
   6:libopenssl1_0_0-1.0.2p-3.14.1    ############################# [100%]
==============================================================================

Wait for the update to finish.

Warning messages can be ignored

  1. Verify that the OpenSSL packages are upgraded successfully by running

rpm -qa |egrep 'libopenssl1_0_0-1|openssl-1_0_0-1|libopenssl-1'

Example:
==============================================================================
# rpm -qa |egrep 'libopenssl1_0_0-1|openssl-1_0_0-1|libopenssl-1'
libopenssl1_0_0-1.0.2p-3.48.1.x86_64
openssl-1_0_0-1.0.2p-3.48.1.x86_64
libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64
==============================================================================

  1. This step is applicable only for PPMA 3.2 alone, remove OpenSSL 1.1 version

rpm -evh openssl-1_1-1.1.1d-2.39.2.x86_64 libopenssl1_1-1.1.1d-2.39.2.x86_64
Example:
==============================================================================
# rpm -evh openssl-1_1-1.1.1d-2.39.2.x86_64 libopenssl1_1-1.1.1d-2.39.2.x86_64
Preparing...    ################################# [100%]
Cleaning up / removing...
   1:openssl-1_1-1.1.1d-2.39.2   ################################# [ 50%]
   2:libopenssl1_1-1.1.1d-2.39.2  ################################# [100%]
==============================================================================

  1. Start OpenSSL, Tomcat, Apache, and Data Collector services using systemctl commands

systemctl start sshd.service
systemctl start tomcat
systemctl start apache2
systemctl start datacollector

Wait for the services to start and launch PPMA GUI

NOTE: If the user upgrades PPMA from v3.1 to v3.2 after updating OpenSSL, post PPMA 3.2 upgrade user must do OpenSSL upgrades on PPMA 3.2 instance also.


Steps to upgrade PPMA 3.0 or 3.0 P01 OVA or VMware Hyper-V (VHD)

About this task
Upgrade of OpenSSL packages in PowerPath Management Appliance Version 3.0 or 3.0 P1 using the upgrade .zip file. You must have root privileges to carry out the upgrade.

Prerequisites:
Download the Powerpath-Openssl_Patch_OVA_VHD_3.0.zip from the attachments of this KB. This .zip file contains the latest OpenSSL packages.

  1. SSH into the PowerPath Management Appliance

  2. Download the "Powerpath-Openssl_Patch_OVA_VHD_3.0.zip" file to a known folder location on PPMA

  3. Change to the directory in which the downloaded .zip file is copied.

cd <upgrade_package_directory>

  1. Extract the .zip file contents.

unzip Powerpath-Openssl_Patch_OVA_VHD_3.0.zip

  1. Change to the Powerpath-Openssl_Patch_OVA_VHD_3.0 folder.

cd Powerpath-Openssl_Patch_OVA_VHD_3.0

  1. Stop OpenSSL, Tomcat, Apache, and Data Collector services using systemctl commands

systemctl stop sshd.service
systemctl stop tomcat
systemctl stop apache2
systemctl stop datacollector

  1. Upgrade the OpenSSL packages using RPM command

rpm -Uvh --nosignature  libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm libopenssl1_0_0-1.0.2j-60.75.1.x86_64.rpm openssl-1.0.2j-60.75.1.x86_64.rpm
Example:
==============================================================================
# rpm -Uvh --nosignature libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm libopenssl1_0_0-1.0.2j-60.75.1.x86_64.rpm openssl-1.0.2j-60.75.1.x86_64.rpm
Preparing...                      ################################# [100%]
Updating / installing...
   1:libopenssl1_0_0-1.0.2j-60.75.1   ############################# [ 17%]
   2:openssl-1.0.2j-60.75.1           ############################# [ 33%]
   3:libopenssl-devel-1.0.2j-60.75.1  ############################# [ 50%]
Cleaning up / removing...
   4:libopenssl-devel-1.0.2j-60.60.1  ############################# [ 67%]
   5:openssl-1.0.2j-60.60.1           ############################# [ 83%]
   6:libopenssl1_0_0-1.0.2j-60.60.1   ############################# [100%]
==============================================================================

Wait for the update to finish.

Warning messages can be ignored

  1. Verify that the OpenSSL packages are upgraded successfully by running

rpm -qa |egrep 'libopenssl1-devel|openssl|libopenssl'

Example:
==============================================================================
# rpm -qa |egrep 'libopenssl1-devel|openssl|libopenssl'
openssl-1.0.2j-60.75.1.x86_64
libopenssl1_0_0-1.0.2j-60.75.1.x86_64
libopenssl-devel-1.0.2j-60.75.1.x86_64
==============================================================================

  1. Start OpenSSL, Tomcat, Apache, and Data Collector services using systemctl commands

systemctl start sshd.service
systemctl start tomcat
systemctl start apache2
systemctl start datacollector

Wait for the services to start and launch PPMA GUI

NOTE: If the user upgrades PPMA from v3.0 or v3.0 P1 to v3.1 after updating OpenSSL, post PPMA 3.1 or later upgrade user must do OpenSSL upgrade instance also.


Steps to upgrade PPMA 3.2 Docker Container (TBZ)

About this task
Upgrade of OpenSSL packages in PowerPath Management Appliance Version 3.2 by using the upgrade .zip file in Docker environment. You must have root privileges to carry out the upgrade.

For PPMA 3.2 P01 and 3.2 SP1, see "Steps to upgrade PPMA 3.1 Docker Container (TBZ)" section.

This package is applicable only for PPMA 3.2.

Prerequisites:
Download the Powerpath-Openssl_Patch_Docker_3.2.zip from the attachments of this KB. This .zip file contains the latest OpenSSL tar file and Dockerfile.

  1. In the PowerPath Management Appliance web console, go to Help > Export Config ZIP and save the resulting PowerPath_Management_Appliance.zip file to the local desktop or a remote location.

  2. SSH into the Linux host where the PPMA docker container is deployed.

  3. Download the Powerpath-Openssl_Patch_Docker_3.2.zip file to a known folder location on the Linux host

  4. Change to the directory where the .zip file has been copied or downloaded.

cd <upgrade_package_directory>

  1. Extract the .zip file. This unpacks the "Powerpath-Openssl_Patch_Docker_3.2" directory and all its contents

unzip Powerpath-Openssl_Patch_Docker_3.2.zip

  1. Change to the Powerpath-Openssl_Patch_Docker_3.2 folder.

cd Powerpath-Openssl_Patch_Docker_3.2

  1. Stop the already running PPMA docker container using the docker stop command on your Linux host

docker stop <container_ID>

The "docker ps" command displays information about the containers that are currently running. You can obtain the <container ID> with this command

Example:
==============================================================================
# docker ps
CONTAINER ID   IMAGE   COMMAND    CREATED    STATUS   PORTS       NAMES
7afbbefec519   powerpath:latest   ...        ...      0.0.0.0:8080 ppma
==============================================================================

  1. You can see the list of Docker images on your linux host by issuing the following command.

docker images

The output displays downloaded images and their tags (version numbers).

Example:
==============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB

==============================================================================

Write down the PowerPath Docker Image name and its TAG name that was initially imported.

  1. Modify the Dockerfile present in the current directory with the existing PowerPath Docker image name and TAG name that was obtained in "Step 8" and save the file

==============================================================================
vi Dockerfile

FROM <PowerPath Docker image name from Step8>:<TAG>
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p- 3.42.2.x86_64.rpm libopenssl1_0_0-1.0.2p- 3.42.2.x86_64.rpm openssl-1_0_0-1.0.2p- 3.42.2.x86_64.rpm
RUN rpm -evh openssl-1_1-1.1.1d-2.33.1.x86_64 libopenssl1_1-1.1.1d-2.33.1.x86_64
==============================================================================

Only the highlighted entry must be updated, and the file saved

Example:

==============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB

# vi Dockerfile
FROM powerpath:latest
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm
RUN rpm -evh openssl-1_1-1.1.1d-2.33.1.x86_64 libopenssl1_1-1.1.1d-2.33.1.x86_64
==============================================================================

  1. Once the Dockerfile has been updated, you can build a new docker image. Specify the folder path where the Dockerfile is located. The -t flag enables you to tag the new image with a new name

docker build -t <New_PPMA_Container_Name> </path/to/Dockerfile>
      
Example:
==============================================================================
# docker build -t powerpath-3.2-patched /root/Powerpath-Openssl_Patch_Docker
Sending build context to Docker daemon 6.139 MB
Step 1: FROM powerpath:latest
 ---> 9b8599e3e7a0
Step 2: ADD openssl.tar /opt/ADG/
 ---> 1cc3e9ae2013
Removing intermediate container 23ae93140bde
Step 3: RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm
 ---> Running in 134c466e6374
warning: libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY
Preparing...                          ########################################
Updating / installing...
libopenssl1_0_0-1.0.2p-3.48.2         ########################################
libopenssl-1_0_0-devel-1.0.2p-3.48.2  ########################################
openssl-1_0_0-1.0.2p-3.48.2           ########################################
Cleaning up / removing...
openssl-1_0_0-1.0.2p-3.14.1           ########################################
libopenssl-1_0_0-devel-1.0.2p-3.14.1  ########################################
libopenssl1_0_0-1.0.2p-3.14.1         ########################################
Removing intermediate container 3bafc7a53a78
---> 95b7285305a2
Step 4/4 : RUN rpm -evh openssl-1_1-1.1.1d-2.33.1.x86_64 libopenssl1_1-1.1.1d-2.33.1.x86_64
---> Running in d5049c8ea6d6
Preparing...                          ########################################
Cleaning up / removing...
openssl-1_1-1.1.1d-2.33.1             ########################################
libopenssl1_1-1.1.1d-2.33.1           ########################################
Removing intermediate container d5049c8ea6d6
---> 29d8ccb49a0c
Successfully built 29d8ccb49a0c
Successfully tagged ppma32_b78_svt_test_patched:latest

==============================================================================

  1. Verify the new docker image with the following command

docker images

This will output the newly created docker image alongside the other base images

Example:

==============================================================================
# docker images
REPOSITORY             TAG               IMAGE ID            CREATED      SIZE
powerpath-3.2-patched   latest     7d36c440515e        4 minutes ago    2.13 GB
powerpath               latest     9b8599e3e7a0        2 weeks ago      2.10 GB

==============================================================================

Write down the new docker image name.

  1. Running the PPMA Docker Image:

See Step 2 in "Deploying the Dell PowerPath Management Appliance (TBZ)" section in PPMA IAG guide to start the newly created docker container using the Image name from "Step 11."

NOTE: If any folders are mapped for PPMA log persistence, remove the old logs from the mapped folder.

  1. Import the config file to newly deployed PPMA docker

Log in to PPMA UI and go to System > Settings > Import Config ZIP and then import the PowerPath_management_appliance.zip file which you exported in "Step 1"

  1. Remove the previous docker container

docker rm <old_container_ID>

  1. Remove the old docker image

docker rmi <old_Docker_Image_Name_from_Step7>

 

Steps to upgrade PPMA3.1, 3.2P01, 3.2SP1 Docker Container (TBZ)

About this task
Upgrade of OpenSSL packages in PowerPath Management Appliance Version 3.1 by using the upgrade .zip file in Docker environment. You must have root privileges to carry out the upgrade.

For PPMA 3.2 version, see "Steps to upgrade PPMA 3.2 Docker Container (TBZ)" section.

Prerequisites:
Download the Powerpath-Openssl_Patch_Docker_3.1_3.2SP1.zip from the attachments of this KB. This .zip file contains the latest OpenSSL tar file and Dockerfile.

  1. In the PowerPath Management Appliance web console, go to Help > Export Config ZIP and save the resulting PowerPath_Management_Appliance.zip file to the local desktop or a remote location.

  2. SSH into the Linux host where the PPMA docker container is deployed.

  3. Download the Powerpath-Openssl_Patch_Docker_3.1_3.2SP1.zip file to a known folder location on the Linux host

  4. Change to the directory where the .zip file has been copied or downloaded.

cd <upgrade_package_directory>

  1. Extract the .zip file. This unpacks the "Powerpath-Openssl_Patch_Docker_3.1_3.2SP1" directory and all its contents

unzip Powerpath-Openssl_Patch_Docker_3.1_3.2SP1.zip

  1. Change to the Powerpath-Openssl_Patch_Docker_3.1 folder.

cd Powerpath-Openssl_Patch_Docker_3.1_3.2SP1

  1. Stop the already running PPMA docker container using the docker stop command on your Linux host

docker stop <container_ID>

The "docker ps" command displays information about the containers that are currently running. You can obtain the <container ID> with this command

Example:
==============================================================================
# docker ps
CONTAINER ID   IMAGE   COMMAND    CREATED    STATUS   PORTS       NAMES
7afbbefec519   powerpath:latest   ...        ...      0.0.0.0:8080 ppma
==============================================================================

You can see the list of Docker images on your linux host by issuing the following command.

docker images

The output displays downloaded images and their tags (version numbers).

Example:
==============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB
==============================================================================

Write down the PowerPath Docker Image name and its TAG name that was initially imported.

  1. Modify the Dockerfile present in the current directory with the existing PowerPath Docker image name and TAG name that was obtained in "Step 8" and save the file

==============================================================================

vi Dockerfile

FROM <PowerPath Docker image name from Step8>:<TAG>
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm 
=============================================================================

Only the highlighted entry must be updated, and the file saved

Example:
=============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB

# vi Dockerfile
FROM powerpath:latest
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm
=============================================================================

  1. Once the Dockerfile has been updated, you can build a new docker image. Specify the folder path where the Dockerfile is located. The -t flag enables you to tag the new image with a new name

docker build -t <New_PPMA_Container_Name> </path/to/Dockerfile>
      
Example:
=============================================================================
# docker build -t powerpath-3.1-patched /root/Powerpath-Openssl_Patch_Docker
Sending build context to Docker daemon 6.139 MB
Step 1: FROM powerpath:latest
 ---> 9b8599e3e7a0
Step 2: ADD openssl.tar /opt/ADG/
 ---> 1cc3e9ae2013
Removing intermediate container 23ae93140bde
Step 3: RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm libopenssl1_0_0-1.0.2p-3.48.1.x86_64.rpm openssl-1_0_0-1.0.2p-3.48.1.x86_64.rpm
 ---> Running in 134c466e6374
warning: libopenssl-1_0_0-devel-1.0.2p-3.48.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY
Preparing...                          ########################################
Updating / installing...
libopenssl1_0_0-1.0.2p-3.48.2         ########################################
libopenssl-1_0_0-devel-1.0.2p-3.48.2  ########################################
openssl-1_0_0-1.0.2p-3.48.2           ########################################
Cleaning up / removing...
openssl-1_0_0-1.0.2p-3.14.1           ########################################
libopenssl-1_0_0-devel-1.0.2p-3.14.1  ########################################
libopenssl1_0_0-1.0.2p-3.14.1         ########################################
---> 7d36c440515e
Removing intermediate container 134c466e6374
Successfully built 7d36c440515e
=============================================================================

  1. Verify the new docker image with the following command

docker images

This outputs the newly created docker image alongside the other base images

Example:
=============================================================================
# docker images
REPOSITORY             TAG               IMAGE ID            CREATED      SIZE
powerpath-3.1-patched   latest     7d36c440515e        4 minutes ago    2.13 GB
powerpath               latest     9b8599e3e7a0        2 weeks ago      2.10 GB
=============================================================================


Write down the new docker image name.

  1. Running the PPMA Docker Image:

See Step 2 in "Deploying the Dell PowerPath Management Appliance (TBZ)" section in PPMA IAG guide to start the newly created docker container using the Image name from "Step 11."

NOTE: If any folders are mapped for PPMA log persistence, remove the old logs from the mapped folder.

  1. Import the config file to newly deployed PPMA docker

Log in to PPMA UI and go to System > Settings > Import Config ZIP and then import the PowerPath_management_appliance.zip file which you exported in "Step 1"

  1. Remove the previous docker container

docker rm <old_container_ID>

  1. Remove the old docker image

docker rmi <old_Docker_Image_Name_from_Step7>

 

Steps to upgrade PPMA3.0 and 3.0 P01 Docker Container (TBZ)

About this task
Upgrade of OpenSSL packages in PowerPath Management Appliance Version 3.0 by using the upgrade .zip file in Docker environment. You must have root privileges to carry out the upgrade.

Prerequisites:
Download the Powerpath-Openssl_Patch_Docker_3.0.zip from the attachments of this KB. This .zip file contains the latest OpenSSL tar file and Dockerfile.

  1. In the PowerPath Management Appliance web console, go to Help > Export Config ZIP and save the resulting PowerPath_Management_Appliance.zip file to the local desktop or a remote location.

  2. SSH into the Linux host where the PPMA docker container is deployed.

  3. Download the Powerpath-Openssl_Patch_Docker_3.0.zip file to a known folder location on the Linux host

  4. Change to the directory where the .zip file has been copied or downloaded.

cd <upgrade_package_directory>

  1. Extract the .zip file. This unpacks the "Powerpath-Openssl_Patch_Docker_3.0" directory and all its contents

unzip Powerpath-Openssl_Patch_Docker_3.0.zip

  1. Change to the Powerpath-Openssl_Patch_Docker_3.0 folder.

cd Powerpath-Openssl_Patch_Docker_3.0

  1. Stop the already running PPMA docker container using the docker stop command on your Linux host

docker stop <container_ID>

The "docker ps" command displays information about the containers that are currently running. You can obtain the <container ID> with this command.

Example:
=============================================================================
# docker ps
CONTAINER ID   IMAGE   COMMAND    CREATED    STATUS   PORTS       NAMES
7afbbefec519   powerpath:latest   ...        ...      0.0.0.0:8080 ppma
=============================================================================

  1. You can see the list of Docker images on your linux host by issuing the following command.

docker images

The output displays downloaded images and their tags (version numbers).

Example:
=============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB
=============================================================================

Write down the PowerPath Docker Image name and its TAG name that was initially imported.

  1. Modify the Dockerfile present in the current directory with the existing PowerPath Docker image name and TAG name that was obtained in "Step 8" and save the file

=============================================================================

vi Dockerfile

FROM <PowerPath Docker image name from Step8>:<TAG>
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl &&  libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm libopenssl1_0_0-1.0.2j-60.75.1.x86_64.rpm openssl-1.0.2j-60.75.1.x86_64.rpm
=============================================================================

Only the highlighted entry must be updated, and the file saved.

Example:
=============================================================================
# docker images
REPOSITORY          TAG         IMAGE ID            CREATED       SIZE
powerpath           latest       9b8599e3e7a0      2 weeks ago    2.101 GB

# vi Dockerfile
FROM powerpath:latest
ADD openssl.tar /opt/ADG/
RUN cd /opt/ADG/openssl && rpm -Uvh --nodeps libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm libopenssl1_0_0-1.0.2j-60.75.1.x86_64.rpm openssl-1.0.2j-60.75.1.x86_64.rpm
=============================================================================

  1. Once the Dockerfile has been updated, you can build a new docker image. Specify the folder path where the Dockerfile is located. The -t flag enables you to tag the new image with a new name

docker build -t <New_PPMA_Container_Name> </path/to/Dockerfile> 

Example:
=============================================================================
# docker build -t powerpath-3.0-patched /root/Powerpath-Openssl_Patch_Docker
Sending build context to Docker daemon  1.972MB
Step 1/3 : FROM ppma30p1b19:latest
 ---> 6c84a9e58daf
Step 2/3 : ADD openssl.tar /opt/ADG/
 ---> Using cache
 ---> 655422a7a058
Step 3/3 : RUN cd /opt/ADG/ && rpm -Uvh --nodeps libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm libopenssl1_0_0-1.0.2j-60.75.1.x86_64.rpm openssl-1.0.2j-60.75.1.x86_64.rpm
 ---> Running in c1730d2f4407
warning: libopenssl-devel-1.0.2j-60.75.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY
Preparing...                          ########################################
Updating / installing...
libopenssl1_0_0-1.0.2j-60.75.1        ########################################
openssl-1.0.2j-60.75.1                ########################################
libopenssl-devel-1.0.2j-60.75.1       ########################################
Cleaning up / removing...
libopenssl-devel-1.0.2j-60.60.1       ########################################
openssl-1.0.2j-60.60.1                ########################################
libopenssl1_0_0-1.0.2j-60.60.1        ########################################
Removing intermediate container c1730d2f4407
 ---> 0751068f3a83
Successfully built 0751068f3a83
Successfully tagged ppma30p1b19_openssl:latest
=============================================================================

  1. Verify the new docker image with the following command

docker images

This outputs the newly created docker image alongside the other base images.

Example:
=============================================================================
# docker images
REPOSITORY             TAG               IMAGE ID            CREATED      SIZE
powerpath-3.0-patched   latest     7d36c440515e        4 minutes ago    2.13 GB
powerpath               latest     9b8599e3e7a0        2 weeks ago      2.10 GB
=============================================================================

Write down the new docker image name.

  1. Running the PPMA Docker Image:

See Step 2 in "Deploying the Dell PowerPath Management Appliance (TBZ)" section in PPMA IAG guide to start the newly created docker container using the Image name from "Step 11."

NOTE: If any folders are mapped for PPMA log persistence, remove the old logs from the mapped folder.

  1. Import the config file to newly deployed PPMA docker

Log in to PPMA UI and go to System > Settings > Import Config ZIP and then import the PowerPath_management_appliance.zip file which you exported in "Step 1"

  1. Remove the previous docker container

docker rm <old_container_ID>

  1. Remove the old docker image

docker rmi <old_Docker_Image_Name_from_Step7>

Legal Information

Article Properties

Last Published Date

26 Apr 2023

Version

2

Article Type

Security KB

Back to Top