Upgrading BMC Helix IT Operations Management from version 24.1 to 24.2

Before you begin

• Make sure you have performed all the steps listed in the Preparing for upgrade topic.
• Delete the Helm revision secrets of Kubernetes cronjob if you upgraded from Kubernetes version 1.24 to 1.25 or later.
  For more information, see Deleting the helm revision secrets of the Kubernetes CronJob.
• Migrate data from PostgreSQL database version 12.9 to 15.x by using the PostgreSQL migration utility.
  For more information, see Migrating-data-from-PostgreSQL-database-12-9-to-15-x.

To upgrade BMC Helix IT Operations Management

1. In the new_working_directory/ configs/deployment.config file, update the following values:
   1. Set the values of the following services to yes.
      • _INFRA
      • _PTPOSTGRES
      • _KAFKA
      • _REDIS
      • _RSSO
      • _VICTORIAMETRICS
      • _ELASTICSEARCH
      • _MINIO
   2. For all the BMC Helix IT Operations Managementservices for which you are licensed, set the value to yes; for all other services, set the value to no.
      For example, if you are only licensed to use BMC Helix Operations Management and BMC Helix Continuous Optimization:

      • To use BMC Helix Operations Management, set the value of MONITOR to yes.

        (Optionally)

        • To use AIOps, set AIOPS_SERVICES to yes.
        • To use Log Analytics, set INTELLI_INT_SERVICES to yes.

      • To use BMC Helix Continuous Optimization, set the value of OPTIMIZE to yes. 
        
        

        Best practice
        To see your licensed product services, navigate to the configs/deployment.config file in BMC Helix IT Operations Management version 24.1.00.

2. From the new working directory (new_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.

3. (Optional) To view the logs during the upgrade, run the following command:

   tail -f logs/deployment.log
4. 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>

Where to go from here

Configuring-after-upgrade