Skip to Content

Issues tables

Review the following table for issues that were corrected in BMC Helix IT Operations Management (BMC Helix ITOM) 25.4 and known issues that remain open.

Related topics

Release notes and notices

Troubleshooting

 

Corrected issues

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 .

Warning

Important

The following table lists all the known issues and only the critical customer and partner reported issues corrected in this release of BMC Helix IT Operations Management .
For information about any particular issue that is not listed in this table, contact BMC Support.

You can also filter and sort issues according to component or defect ID. 

ComponentDescriptionStatusFound InDefect ID
BMC Helix IT Operations Management

The BMC Helix IT Operations Management 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.

Fixed in 25.425.4DRRE3-9221
BMC Helix IT Operations ManagementThe PostgreSQL migration fails because the required chart, bmc-pg-ha-17, is missing.Fixed in 25.425.3DRRE3-9339
BMC Helix IT Operations ManagementDeployment of BMC Helix IT Operations Management fails due to a missing BMC Helix Automation Console parameter value in the infra.config file.Fixed in 25.425.3DRRE3-8991
 
BMC Helix IT Operations Management

The Kibana password in the configMap file is stored in plain text, making it vulnerable to unauthorized access.

Fixed in 25.425.3DRRE3-8973
BMC Helix IT Operations ManagementThe Health Check Tool fails when the encoded certificate body contains the keyword END.Fixed in 25.425.2DRRE3-8782
BMC Helix IT Operations Management

When you run the Trivy scanner, the reports display images with a Kafka client version earlier than 3.8.1:
bmchelix/lp0lz:25200-v113-ade-infra-clients-alpine

bmchelix/lp0lz:25200-v97-bitnami-kafka-3.6.0-rockylinux-9

Fixed in 25.425.2DRRE3-8548
BMC Helix IT Operations ManagementWhen you configure custom security certificates, the ES_JAVA_OPTS and OPENSEARCH_JAVA_OPTS parameters in the OpenSearch and Opendistro StatefulSets display plain-text passwords sourced from ES_JKS_PASSWORD instead of in an encrypted format.Fixed in 25.423.4DRRE3-5799
BMC Helix Dashboards

BMC Helix Dashboards fails to generate a report on the OpenShift stack in BMC Helix IT Operations Management deployment.

Workaround:

Run the following command in the OpenShift cluster where the issue occurs: 
oc set env deployment/adereporting-report-generator-service XDG_CONFIG_HOME=/tmp/.config
 

Or perform the following steps:

  1. Open a terminal and log in to your OpenShift cluster.
  2. Edit the deployment YAML file by running the following command:
    oc edit deployment/adereporting-report-generator-service -n namespace
  3. In the container env section, add the following parameters:
       - name: XDG_CONFIG_HOME
         value: "/tmp/.config"
  4. Save and exit the editor.
    When you reopen the editor, new pods for the adereporting-report-generator-service start with the updated environment variable.
Open25.3DRJ71-19532
BMC Helix Dashboards

The BMC Helix Dashboards platform URL fails to update in environments that use NGINX Plus ingress controller. This issue causes the platform URL to become unreachable, prevents the addition of data sources, and gives the following error:

platform_url not reachable

Workaround:

In the Dashboard API for Service Management, the Platform URL was not updated with the correct value in the dashboards/connections/datasources/edit configuration.

  1. Access the PostgreSQL Kubernetes Pod and connect to the reportdb database.
  2. Locate the affected datasource by using its UID and update the json_data field with the correct platform URL.
  3. Delete any existing adereporting-ootb-content job, then rerun the upgrade command to reload the content according to the deployment logs for adereporting-ootb-content.
  4. Run the rerun command from the /helix-on-prem-deployment-manager directory. This command deploys a fresh job.
Open25.3DRJ71-18300

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix IT Operations Management deployment 25.4