C50 Container Deployment Fails to Connect to vPCA

Products

• AppNeta

Issue/Introduction

The C50 container deployment fails to connect to the vPCA when installing version 17․0․2 via Podman ․​​​‌​‍

Environment

 

• OS: RHEL 9․7

• Application: vPCA 18․13․1 , EMP 16․3․1

• Component: C50 Container (Podman 5․x․0 )

   

   

 

Cause

The vPCA 18.13.1 On-Prem version does not support c50 EMP higher than 16.3.1. The installer pulled down the 17.0.2 version and was unable to connect to the On-Prem instance.

Resolution

Steps to Resolve

1․ UNINSTALL CURRENT VERSION Command: sudo ․/setup․sh uninstall EXPECTED: The 17․0․2 version uninstalls successfully

2․ CLEAN UP OLD TOOLS.

       Command:
           rm -f /tmp/cmp-tools*

       EXPECTED: Previous tools are removed from the temporary directory

 

3․ REMOVE C50 FOLDER
  
      Command:
           rm -Rf [folderName]
 
      NOTE: Delete the directory where the compose file was extracted to ensure downloaded tools are removed

 

4․ EXTRACT NEW PODMAN FILE.

       Command:
             tar -xvzf compose․[containerName]․tar․gz

       EXPECTED: Files extract successfully

 

5․ MODIFY CONFIGURATION FILE Path: ․env Add the following two lines:
  
    CMP_IMAGE_TAG=16.3.1.57665
    CONTAINER_REGISTRY=appneta.azurecr.io


     EXPECTED: File saves successfully with specific supported version

 

 

6․ REINSTALL C50
  
       Command:
              sudo ․/setup․sh install


      WARNING: If the script asks to update tools, answer "no"
    EXPECTED: Installation completes and C50 connects to vPCA

 

 

VERIFY SUCCESS:

• C50 container shows up connected in vPCA

• Podman lists the containers as healthy