Applying the hotfix 26.1.00.001

This topic describes how to apply the hotfix 26.1.00.001 on an environment where BMC Helix IT Operations Management 26.1.00 is already deployed. The hotfix 26.1.00.001 includes optimized sizing requirements.

Use this procedure if BMC Helix ITOM 26.1.00 is already deployed and you want to apply hotfix 26.1.00.001.

Before you begin

• Make sure BMC Helix IT Operations Management 26.1.00 is already deployed.
• You have the required Kubernetes cluster access to delete the ConfigMaps in the target namespace.

To apply the hotfix 26.1.00.001

1. Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.
2. Download the hotfix itom-predeploy-hotfix-26.1.00.001-3.tar.gz from EPD  and save it in the workspace directory.
   The hotfix 26.1.00.001 includes optimized sizing requirements.
   

3. To extract the hotfix, run the following command:

   tar -xvf itom-predeploy-hotfix-26.1.00.001-3.tar.gz

   The updated files will replace the affected files in the workspace directory.

4. Verify that the properties in the helix-on-prem-deployment-manager/configs/infra.config and helix-on-prem-deployment-manager/configs/deployment.config files are configured as required.
   For more information, see Configuration file settings.

5. In the helix-on-prem-deployment-manager/configs/deployment.config file, set the INSTALL_MODE parameter to upgrade.

6. Delete the configmap helix-install-status-26.1.00 by running the following command:

   kubectl -n <namespace> delete cm helix-install-status-26.1.00

7. To deploy BMC Helix ITOM hotfix 26.1.00.001, run the following command:

   Important

   • The passwords that you entered in the commons/certs/secrets.txt file are encrypted. The deployment manager does not pause to ask for the encryption or decryption of a password. The deployment manager generates a random password to encrypt or decrypt all passwords added to the secrets.txt file.
   • Make sure that the passwords used during the previous deployment have not changed.
     • If the passwords have not changed since the last deployment, no action is required.
     • If the passwords have changed, perform the following steps before rerunning the deployment manager:
       • Delete the secrets directory from the commons/certs directory.
       • Recreate the secrets.txt file with the updated passwords.

   ./deployment-manager.sh