Issues tables

View the issues in the following tables by the default sort order, Status, which shows the corrected issues first.

The version number represents the update (Year.Month.Release) or release number (MajorRelease.MinorRelease.ServicePack.Patch) in which the issue is fixed.

To view only the open issues, click the Status filter, and select Open.

BMC Helix Service Management upgrade fails at the HelixGPT Apps stage when the environment lacks internet access, causing the pods to attempt to fetch files from huggingface.co.

Workaround:

1. Log in to BMC Deployment Engine.
2. Run the following command:
   kubectl get deployment -n <BMC Helix Innovation Suite> |grep -i gpt
   Sample command output:
   helix-gpt-assistant            1/1     1            1           45d
   helix-gpt-data-connection      1/1     1            1           45d
    
3. To edit the helix-gpt-assistant deployment, run the following command:
   kubectl edit deployment helix-gpt-assistant -n <BMC Helix Innovation Suite namespace>
    
4. In the helix-gpt-assistant deployment, add the following environment variable:
   - name: ONLY_USE_LOCAL_HF_CACHE
     value: 'true'
5. To edit the helix-gpt-data-connection deployment, run the following command:
   kubectl edit deployment helix-gpt-data-connection -n <BMC Helix Innovation Suite namespace>
6. In the helix-gpt-data-connection deployment, add the following environment variable:
   - name: ONLY_USE_LOCAL_HF_CACHE
     value: 'true'

The BMC Helix Platform Common Services container image, lp0lz-redis-cluster, has a security vulnerability identified as CVE-2025-49844.

For more information about the vulnerability, see CVE-2025-49844 Detail

If the sr-input-file.sh file is missing in CUSOTMER_CONFIGS repository, the HELIX_DB_REFRESH pipeline fails to execute successfully.

Workaround:

1. In your Smart Reporting environment, create a copy of the sr-input-file.sh file.
2. In your source BMC Helix Service Management environment, perform the following steps:
   1. To create the onprem-remedyserver-config directory, run the following command:
      git clone onprem-remedyserver-config.git
   2. Copy the sr-input-file.sh file you created in step 1 to the /home/git/git_repo/CUSTOMER_CONFIGS/onprem-remedyserver-config/customer/<CUSTOMER_SERVICE> location.
   3. To commit the changes, run the following commands:git add -A
      git commit -am "sr input file added"
      git push origin master

       

3. In your target BMC Helix Service Management environment, perform steps 2a to 2c.
4. Copy the SOURCE_CUSTOMER_CONFIGS and TARGET_CUSTOMER_CONFIGS repositories to the environment where you want to run the database refresh pipeline.
   For example, to run the database refresh pipeline in the target environment, make sure that the following repositories are present in the git repository of the target environment:
   • SOURCE_CUSTOMER_CONFIGS
   • TARGET_CUSTOMER_CONFIGS
   • DB_REFRESH_REPO

During the execution of the HELIX_DB_REFRESH pipeline, the user interface does not provide an option to skip component stages that are not being used.

Workaround:

1. To bypass a stage for a specific component, create blank placeholder files with designated names and place them in the following directory:  
   <CUSTOM WORKSPACE LOCATION>/HELIX_DB_REFRESH/completedtasks
2. Run the HELIX_DB_REFRESH pipeline by using the RERUN option.

During the upgrade of BMC Helix Service Management to version 25.3.01, the HELIX_ONPREM_DEPLOYMENT pipeline might become stuck at the platform rolling upgrade or platform FTS stage if any FTS pods are already down before the rolling restart begins.

Workaround: Delete all the pods from the respective stateful set. To force a fresh start, manually delete the pods using the following command:
kubectl delete pod <pod name>

25.4.01,

25.3.01

DRD21-127368

DRD21-128076

BMC Digital Workplace

When you change the hannah_admin user password after installing BMC Helix Innovation Suite, the dwp-tomcat-deployment-master and dwp-tomcat-deployment-slave pods fail and do not start.

Workaround: In the BMC Digital Workplace Tomcat configuration, update the hannah_admin user password, and then restart the dwp-tomcat-deployment-master and dwp-tomcat-deployment-slave pods.

Open

25.4.01,
25.3.01,

25.2.01,

25.1.01,
23.3.04,
23.3.01,
22.1.06,

21.3.06,

21.3.05,

21.3.04

BMC Helix Platform Common Services

You cannot log in to Helix Portal if you do not specify a value for the SMTP_PASSWORD parameter in the secrets.txt file during a BMC Helix Platform services installation.

Workaround: In the secrets.txt file, specify a placeholder value for the SMTP_PASSWORD parameter.

Open

25.4.01,
25.3.01,

25.2.01,

25.1.01,
23.3.04,
23.3.01,

22.1.06,

21.3.06,

21.3.05

DRRE3-1892

Clam AV

Clam AntiVirus pod fails in any of the following cases:

• You are using an air-gapped environment and do not have access to internet.
• You are not using an air-gapped environment and have access to internet. However, you encounter the following warning:
  WARNING: Mon Jul  3 10:55:25 2023 -> FreshClam received error code 429 from the ClamAV Content Delivery Network (CDN).
  Mon Jul  3 10:55:25 2023 ->  2. If you have more than 10 hosts on your network attempting to download,
  Mon Jul  3 10:55:25 2023 ->     it is recommended that you set up a private mirror on your network using
  Mon Jul  3 10:55:25 2023 ->     cvdupdate (https://pypi.org/project/cvdupdate/) to save bandwidth on the
  Mon Jul  3 10:55:25 2023 ->     CDN and your own network.
  Mon Jul  3 10:55:25 2023 ->  3. Please do not open a ticket asking for an exemption from the rate limit,
  Mon Jul  3 10:55:25 2023 ->     it will not be granted.
  WARNING: Mon Jul  3 10:55:25 2023 -> You are on cool-down until after: 2023-07-03 19:47:57

Workaround:

If you are using an air-gapped environment, perform the following steps:

1. Scale down the Clam AV deployment to zero.

2. On the AR System Configuration Generic UI form, set the configuration setting Enable-Attachment-Validation-Plugin value as false.
   See Configuration settings E-M.

If your environment has access to internet, unwait till the cool-down period is complete.

Open

25.4.01,
25.3.01,

25.2.01,

25.1.01
23.3.04,
23.3.01,
22.1.06

DRD21-61101