Upgrading BMC Helix IT Operations Management from version 25.1 to 25.2


Upgrade BMC Helix IT Operations Management (BMC Helix ITOM) from version 25.1.00 to 25.2.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.

 

To upgrade BMC Helix IT Operations Management

  1. From the new working directory (working_directory), run the deployment manager to upgrade BMC Helix IT Operations Management:

    ./deployment-manager.sh

    If you have turned on disaster recovery, the system will prompt you to turn it off. Type y to disable the disaster recovery and continue with upgrade. If you type n, the upgrade will be terminated.

    After the upgrade, you will get the following message:
    Completed Helix On-prem Upgrade.

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

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

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*