Issues tables

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.
   After saving the changes, new pods for the adereporting-report-generator-service start with the updated environment variable.

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:

1. In the Dashboard API for Service Management, the Platform URL was not updated with the correct value in the dashboards/connections/datasources/edit configuration.
2. Access the PostgreSQL Kubernetes Pod and connect to the reportdb database.
3. Locate the affected datasource by using its UID and update the json_data field with the correct platform URL.
4. 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.
   Run the rerun command from the /helix-on-prem-deployment-manager directory. This command deploys a fresh job.

When accessing the AIOps Service or Situation page, the UI might hang or fail to load completely.

This occurs because of intermittent issues in the UI rendering process, which can cause the page to remain blank or get stuck in a loading state, affecting access to AIOps services and situation analysis.

In OnPrem stack deployments with version 25.2.00, even if the BHCO (BMC Helix Capacity Optimization) product is disabled (i.e., Optimize="No" in the deployment.config file or via installer options), the related infrastructure components are still deployed. This includes BHCO-related Victoria Metrics Aggregate services such as:

• victoria-metrics-aggregate-vmstorage-agg
• victoria-metrics-aggregate-vmselect-agg
• victoria-metrics-aggregate-vminsert-agg

This results in unnecessary resource allocation, potentially affecting sizing and overall system performance.

In on-premises deployments, MinIO may fail the SSL handshake if using a self-signed certificate.

This typically results in errors when accessing or uploading files to MinIO over HTTPS.