Skip to Content

Issues tables

Review the following table for issues that were corrected in BMC Helix IT Operations Management (BMC Helix ITOM) 26.1 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 found version (version in which the issue was found), component, or defect ID. 

ComponentDescriptionStatusFound InDefect ID
BMC Helix Automation Console

The system fails to generate remediation code because the Search API Ingress is missing or configured without a valid Ingress class.

Workaround:

Use one of the following ways:

  • Manually add the Ingress class to the automation-console-truesight-patch-manager-core-remediation-v1-minion Ingress object in the BMC Helix ITOM namespace.
  • Before deploying or upgrading to BMC Helix Automation Console 26.1.00, add the following line under the rempcore section in the  <installation_dir>/products/automationconsole/automationconsole.json file:
    "ingress7.ingress.annotations.kubernetes\\\\.io\\\/ingress\\\\.class": "__ingress_class__",
Open26.1.00DRSMP-16805
BMC Helix IT Operations ManagementWhen you upgrade BMC Helix IT Operations Management, application pods fail to connect to the Redis cluster. This issue occurs when you update the secrets before the Redis cluster is installed.Fixed in 26.1.0025.3.00DRRE3-9530
BMC Helix IT Operations ManagementAfter the Redis cluster restarts, Redis connections drop continuously at the cluster level on Port 6379, even though all pods are stable and healthy.Fixed in 26.1.0025.1.00DRRE3-9186
BMC Helix IT Operations Management

The Health Check Tool shows incorrect CPU and Memory resource warnings during pre-install checks for an ITSMCOMPACT deployment of BMC Helix Platform Common Services.

Fixed in 26.1.0025.1.00DRRE3-9498
BMC Helix IT Operations Management

When you are migrating from PostgreSQL 15 to 17, application pods fail to connect to PostgreSQL 17 and the postgres-bmc-pg-ha-15-pool deployment waits for the rollout to complete.

Fixed in 26.1.0025.3.00DRRE3-9531
BMC Helix IT Operations Management

When you run the BMC Helix IT Operations Management scale‑down script for application pods, no log messages appear after the script enters the sleep 600 phase. Therefore, users cannot confirm whether the script is still running or performing scale‑down operations.

Fixed in 26.1.0025.3.00DRRE3-9921
BMC Helix Dashboards

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

Fixed in 26.1.0025.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

Fixed in 26.1.0025.3DRJ71-18300

 

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

BMC Helix IT Operations Management deployment 26.1