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.

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>

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.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.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

BMC Helix Service Management

While using a PostgreSQL database and installing BMC Helix Service Management in an Amazon Elastic Kubernetes Service (EKS) cluster, the HELIX_PLATFORM_DEPLOY pipeline fails at the AR System database creation stage.

Workaround: Restore the PostgreSQL database dumps manually. See Setting-up-a-PostgreSQL-database.

Open

25.3.01

25.2.01,

25.1.01,
23.3.04,
23.3.01,

22.1.06

DRSE3-2439

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.3.01

25.2.01,

25.1.01
23.3.04,
23.3.01,
22.1.06

DRD21-61101