Upgrading BMC Helix IT Operations Management from version 24.2 to 24.4

Upgrade BMC Helix IT Operations Management (BMC Helix ITOM) from version 24.2.00 to 24.4.00.

You might experience downtime during the upgrade, which is to be expected but does not affect the upgrade.

Before you begin

Make sure you have performed all the steps listed in the Preparing for upgrade topic.
Make sure you backed up the OpenSearch 1.x data.
For more information, see Backing-up-the-OpenSearch-1-x-data.

From the new working directory (working_directory), run the deployment manager to upgrade BMC Helix IT Operations Management:
./deployment-manager.sh
After the upgrade, you will get the following message:
Completed Helix On-prem Installation.
(Optional) To view the logs during the upgrade, run the following command:
tail -f logs/deployment.log
If you have deployed BMC Helix IT Operations Management in a multitenant environment, perform the steps to restore the smart-graph-tenant-config configmap and its content:
1. Copy the contents from the smart-graph-tenant-config configmap file that you backed up before the upgrade.
2. To open the smart-graph-tenant-config configmap, run the command:
  kubectl -n <namespace> edit cm smart-graph-tenant-config
3. Paste the contents that you copied from the backed-up smart-graph-tenant-config configmap file in the new smart-graph-tenant-config configmap and save it.
4. To restart the smart graph controller pod, run the following command:
  kubectl rollout restart deploy/smart-graph-controller -n <namepsace>

The zombie process generation issue on redis-haproxy-monitor pods and Kafka Zookeeper pods is fixed in the
Some content is unavailable due to permissions.
OnPrem v24.4.00.001 hotfix, which addresses the following issues:
- DRRE3-7571
- DRRE3-7638

Perform the following steps to apply the hotfix.

If you are using a local repository for pulling images, then ensure that the local image repository has images mentioned in file all_images_24.4.txt:
- containers.bmc.com/bmc/lp0lz:24400001-v103-ade-infra-clients-alpine
- containers.bmc.com/bmc/lp0lz:24400001-v102-bitnami-zookeeper-3.9.1-alpine-jdk11
Extract the hotfix-24.4.00.001-7-Post.tar.gz file to the 24.4.00 workspace folder.tar -xvf hotfix-24.4.00.001-7-Post.tar.gz
Run the hf_script.sh hotfix script file providing the full path of the 24.4.00 deployment manager directory.
bash hf_script.sh </path/to/directory/24.4.00>/helix-on-prem-deployment-manager
For example: bash hf_script.sh /data/24.4.00/helix-on-prem-deployment-manager

If you are using NGINX Ingress Controller version 1.11.2, the Probable Cause Analysis (PCA) API failing issue is fixed in the

Some content is unavailable due to permissions.

OnPrem v24.4.00.003 hotfix, which addresses the DR0F3-18869 defect.

Perform the following steps to apply the hotfix.

If you are using a local repository for pulling images, then add the following image to the local local all_images_24.4.txt image file:
containers.bmc.com/bmc/la0cz:pca-api-service-7019013-2
Extract the hotfix-24.4.00.003-1-Post.tar.gz file to the 24.4.00 workspace folder.tar -xvf hotfix-24.4.00.003-1-Post.tar.gz
Run the hf_script.sh hotfix script file providing the full path of the 24.4.00 deployment manager directory.
bash hf_script.sh </path/to/directory/24.4.00>/helix-on-prem-deployment-manager
For example: bash hf_script.sh /data/24.4.00/helix-on-prem-deployment-manager

Important

This command creates a new directory named /data/24.4.00/helix-on-prem-deployment-manager_HF1.YYYYMMDDHHMMSS, which is a copy of deployment manager directory.
No changes are made to the earlier deployment manager directory that was passed as the parameter.