Upgrading BMC Helix Platform services version from 21.3.03.001 to 22.2.01

 Upgrade BMC Helix Platform services from version 21.3.03.001 to 22.2.01. If you are using an earlier version of the product, first upgrade the platform to version 21.3.03.001, and then upgrade it to version 22.2.01.

The following image shows the supported upgrade path:

To upgrade BMC Helix Platform services

1. Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.
2. Download the deployment manager BMC_Helix_Platform_Services_for_Service_Management_Version_22.2.01.zip from BMC Electronic Product Distribution (EPD) and extract it, if you haven't already.
   The ZIP file contains the following files:
   
   • helix-on-prem-deployment-manager-22.2.01.sh—This file contains the deployment manager.

1. • jsons_22201_002.bzip2—This file contains the fix for the incorrect deployment file repository location issue.

1. • hotfix-22.2.01.001-17.tar.gz—This file contains the 22.2.01 hotfix 1 artifacts.
2. Download the only_ITSM_configs_22201_003.tar.xz file from EPD, if you haven't already.
   This file contains the latest deployment size templates.
   To download the files from EPD, see Downloading-the-installation-files.

1. Go to the directory where you downloaded the deployment manager from the EPD and give the execute permission to the helix-on-prem-deployment-manager-22.2.01.sh file.
   

2. Self-extract the deployment manager. Run the following command:

   ./helix-on-prem-deployment-manager-22.2.01.sh
   cd helix-on-prem-deployment-manager
3. If you are installing BMC Helix Platform common services on Kubernetes 1.24 version, perform the following steps:
   1. Navigate to the commons directory.
   2. Open the preinstall-checker. sh file.
   3. Comment the code for the Kubernetes version check.
4.  Perform the following steps:
   1. Copy the jsons_22201_002.bzip2 file in the helix-on-prem-deployment-manager directory. 

   2. Unzip the file by running the following command:
      

      tar xvf jsons_22201_002.bzip2

      After you unzip the file, the following folders are replaced in the helix-on-prem-deployment-manager/Products directory:

      • aiops
      • common-services
      • helixdashboard-services
      • intelligentautomation
      • intelligentintegrations
      • itsminsight-services
      • monitor
      • platform
5. Update the deployment size templates.

1. 1. In the helix-on-prem-deployment-manager directory, copy the only_ITSM_configs_22201_003.tar.xz file.
      

   2. Extract the only_ITSM_configs_22201_003.tar.xz file by using the following command:

      tar xvf only_ITSM_configs_22201_003.tar.xz 

      After you unzip the file, the following folders are replaced with the new deployment size templates in the helix-on-prem-deployment-manager directory.
      

      • configs/
      • configs/compact.config
      • configs/compact.json
      • configs/compact_jvm.config
      • configs/small.config
      • configs/small.json
      • configs/small_jvm.config
2. Go to the helix-on-prem-deployment-manager/configs/infra.config file and make the following changes:
   1. Set the ingressAPIversion property to true.
   2. Make sure that the ENVIRONMENT variable has the same value that it had in the preceding version.
   3. Set the correct INGRESS_CLASS for the Kubernetes ingress controller 1.2.0 that you installed earlier.

3. In the helix-on-prem-deployment-manager/configs/infra.config file, modify the following parameters that are environment-specific:

4. Go to the helix-on-prem-deployment-manager/configs/deployment.config file and set the following values:
   
5. If you are using BMC Helix Logging, in the helix-on-prem-deployment-manager/configs/deployment.config file, change the value of the BMC_HELIX_LOGGING parameter to yes.

6. Prepare for password encryption. 
   

   Expand to see the steps:

   1. Go to the commons/certs directory and open the secrets.txt file.

   2. Add the following passwords to this file:
   3. Save the secrets.txt file

   Troubleshooting tip

   Make Sure that you provide all passwords in the secrets.txt file. Even if a single password is not added in the secrets.txt file, the deployment fails with an error.

   Sample secrets.txt file

   # cat commons/certs/secrets.txt
   #Please put the passwords in this file
   IMAGE_REGISTRY_PASSWORD=password123
   SMTP_PASSWORD=""
   SMART_SYSTEM_PASSWORD=password123
   PG_PASSWD=Test2020

   ################## End OF THE FILE ####################

7. Run the deployment manager to upgrade BMC Helix Platform common services by executing the following command:

   ./deployment-manager.sh

   To view the logs during the upgrade, run the following command:

   tail -f logs/deployment.log

To apply the hotfix

1. Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.
2. In the helix-on-prem-deployment-manager/configs/deployment.config file, make sure that the INFRA and _RSSO parameter values are set to yes.
   All other parameters in the file must be set to value no.
   

3. Extract the hotfix file hotfix-<build number>.tar.gz that you downloaded from EPD by using the following command:

   tar xvf hotfix-<build number>.tar.gz

4. Navigate to the hotfix directory by using the following command:

   cd hotfix

5. Run the hotfix script file hf_script.sh by using the following command and pass the full path of the previous deployment manager directory.

   bash hf_script.sh </path/to/directory/22.2.01>/helix-on-prem-deployment-manager

   This command creates a copy of the helix-on-prem-deployment-manager directory. 
   For example:

   bash hf_script.sh /data/22.2.01/helix-on-prem-deployment-manager

   This command creates a new directory named helix-on-prem-deployment-manager_HF1 at /data/22.2.01
   After the hotfix script execution is complete, the Please enter password for encryption/decryption command prompt is displayed.

6. Enter the password.
   

Where to go from here

Upgrading-BMC-Helix-IT-Service-Management-to-21-3-06