Issues tables
Review the following tables for issues that were corrected in BMC Helix Service Management deployment 25.2.01 and for known issues that remain open.
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. | |
Known (open) issues | To view only the open issues, click the Status filter, and select Open. |
| Component | Description | Status | Found in | Defect ID |
| BMC Helix Service Management | Postinstallation of BMC Helix Service Management, you encounter errors while installing locales. Workaround:
| Open | 25.2.01 | DRD21-109422 |
| BMC Helix Service Management | During the upgrade of BMC Helix Service Management to version 25.2.01, the following error occurs if the DB_JDBC_URL parameter is specified but the ORACLE_SERVICE_NAME parameter is not specified in the HELIX_ONPREM_DEPLOYMENT pipeline: HELIX_FULL_STACK_UPGRADE pipeline got failed at Platform Upgrade stage - with java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "configValue" is null Workaround: In the HELIX_ONPREM_DEPLOYMENT pipeline, specify the ORACLE_SERVICE_NAME parameter value, and rerun the pipeline. | Open | 25.2.01 | DRD21-125042 |
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.2.01, 25.1.01, 21.3.06, 21.3.05, 21.3.04 | DRIIT-56643 |
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.2.01, 25.1.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.2.01, 25.1.01, 22.1.06 | DRSE3-2439 |
Clam AV | Clam AntiVirus pod fails in any of the following cases:
Workaround: If you are using an air-gapped environment, perform the following steps:
If your environment has access to internet, unwait till the cool-down period is complete. | Open | 25.2.01, 25.1.01 | DRD21-61101 |