Applying hotfix 25.1.01.001

Before you begin

• Download the BMC_Helix_Innovation_Suite_And_Service_Management_Apps_Version_25.1.01.001.zip file; see Downloading-the-installation-files.
• Confirm access to the container images; see Setting-up-a-Harbor-repository-to-synchronize-container-images.

Task1: To update the Git repositories

1. Log in to the BMC Deployment Engine as a Git user.
2. In your local Git repository, create a backup of the following existing repositories:
   • CUSTOMER_CONFIGS
   • HELM_REPO
   • ITSM_REPO
   • PLAYBOOKS_REPO
   • SMARTAPPS_HELM_REPO
   • SMARTREPORTING_PLAYBOOKS_REPO
   • DB_REFRESH_REPO

   • SMARTREPORTING_HELM_REPO
     For example, create a backup of the ITSM_REPO, PLAYBOOKS_REPO, HELM_REPO, SMARTAPPS_HELM_REPO, and CUSTOMER_CONFIGS repositories located at ssh://<Jenkins server host name>/home/git/Git_Repo.

     Warning

     Important

     • After creating a backup of the repositories, make sure you delete the existing repository folders.
     • Make sure you do not modify or change the location of the LIBRARY_REPO repository.
3. Copy the BMC_Remedy_Deployment_Manager_Configuration_Release_25.1.01.001.zip file that you downloaded from the BMC Electronic Product Distribution (EPD) site to your existing local Git repository.
   For example, copy the BMC_Remedy_Deployment_Manager_Configuration_Release_25.1.01.001.zip file to the local Git repository located at ssh://<Jenkins server host name>/home/git/Git_Repo.
4. In the file system where the Git repository is located, unzip the BMC_Remedy_Deployment_Manager_Configuration_Release_25.1.01.001.zip file.
   For example, in the Git_Repo repository located at ssh://<Jenkins server host name>/home/git/Git_Repo, unzip the BMC_Remedy_Deployment_Manager_Configuration_Release_25.1.01.001.zip file.The BMC_Remedy_Deployment_Manager_Configuration_Release_25.1.01.001.zip file contains the following artifacts:
   • CUSTOMER_CONFIGS
   • HELM_REPO
   • ITSM_REPO
   • PLAYBOOKS_REPO
   • SMARTREPORTING_PLAYBOOKS_REPO
   • SMARTREPORTING_HELM_REPO
   • SMARTAPPS_HELM_REPO
   • DB_REFRESH_REPO

Task 2: To apply the hotfix

1. In the HELIX_ONPREM_DEPLOYMENT pipeline, in the Build History section, select the last build, and click Rebuild.
2. In the PRODUCT-DEPLOY section, select the HELIX_GENERATE_CONFIG and HELIX_PLATFORM_DEPLOY options.
3. In the CUSTOMER-INFO section, specify the DEPLOYMENT_MODE parameter value as SERVICE.
4. Click Rebuild.
   After successful completion of the HELIX_ONPREM_DEPLOYMENT pipeline, run the following command to verify that the platform and application component pods:kubectl get pod -n <namespace>The following image shows an example:
   

Where to go from here

Performing-the-postinstallation-configurations