Chapter 7. Fixed issues

Before this update, there was no documentation warning about the behavior of app-config ConfigMaps containing multiple files when deploying Operator-backed instances of RHDH. As a consequence, users could unknowingly define several app-config files inside one ConfigMap, resulting in unpredictable configuration merge order because keys are sorted alphabetically rather than in the intended sequence.

With this update, the documentation recommends splitting multi-entry app-config ConfigMaps into separate single-entry ConfigMaps and referencing them in the Backstage CR (spec.application.appConfig.configMaps field) in the intended merge order.

RHDHBUGS-3312

Before this release, when the card height mode was set to content, workflow run detail cards (Inputs and Results) could bleed into each other, causing overlapping text and broken layouts.

With this update, a CSS grid layout with proper overflow constraints is implemented and cards display correctly regardless of content size.

RHDHBUGS-3518

Before this update, RHDH Operator metadata informers cached PartialObjectMetadata for every Deployment and StatefulSets in the cluster. On large multi-tenant clusters, this caused out-of-memory crash of the operator.

With this update, the Operator scopes metadata caching to the Deployments and StatefulSets that it manages, reducing memory usage and preventing out-of-memory crashes in clusters with a lot of resources.

RHDHBUGS-3569

Before this update, the TechDocs backend plugin bundled a version of @backstage/plugin-techdocs-node that required a newer @backstage/errors library than the one provided by the RHDH backend. As a consequence, TechDocs failed to generate documentation with the error errors.toError is not a function. With this update, the backend dependency is updated to resolve the version mismatch. As a result, TechDocs documentation generation works as expected.

RHDHBUGS-3360

Before this update, when the install-dynamic-plugins init container received a SIGTERM signal during a pod rolling update, eviction, or scale-down, child processes such as skopeo and npm were not terminated. As a consequence, these orphaned processes continued running until Kubernetes sent SIGKILL after the termination grace period, delaying pod shutdowns.

With this update, the init container shell wrapper forwards SIGTERM to the entire process group, ensuring all child processes are terminated immediately. As a result, pod shutdowns during dynamic plugin installation complete in under 5 seconds.

RHDHBUGS-3449

Before this update, an Operator update caused Orchestrator and Lightspeed dynamic plugins to resolve to older package versions. As a consequence, several UI features broke. With this update, the catalog digests are corrected. As a result, the plugins resolve to the correct versions, and the features function properly.

RHDHBUGS-3503

Lightspeed Core Service has been updated to version 0.5.3 to fix multiple CVEs.

RHDHBUGS-3546

Before this update, users were not able to configure custom thresholds for the Filecheck, Openssf and Dependabot Scorecard modules due to reliance on modules for threshold handling.

With this release, a standard threshold configuration format that can be specified for each Scorecard module is available.

RHDHBUGS-3203

Before this update, the background color of the My groups menu was black, making it impossible to read the contents.

With this release, the background color is changed.

RHDHBUGS-3286

Before this update, selecting Bitbucket Cloud or Bitbucket Server as the repository host in a Software Template did not display the workspace and project fields in the repoUrlPicker.

With this release, Bitbucket-specific fields are rendered correctly.

RHDHBUGS-3288

Before this update, when a GitHUB SAML SSO session expired, users would experience a 403 error despite having valid tokens.

With this update, you can add a GitHub SAML SSO check step to your workflows. If the check detects a SAML SSO expiration, a re-authentication prompt appears.

RHDHBUGS-3290

Before this update, steps in Orchestrator form that should have been skipped when they do not apply were still shown.

With this update, those steps are hidden when they are not relevant.

RHDHBUGS-3291

Before this update, there was an issue with filtering Orchestrator workflows. When filtering workflow runs by status and date, a schema-related error would appear.

With this release, lists load as expected when those filters are used.

RHDHBUGS-3292

Before this update, there was an issue with using custom widgets provided by the Orchestrator form plugin. The fields marked with "ui:hidden": true rendered their container element in the workflow form. As a result, large blank spaces appeared between visible fields.

With this update, hidden fields collapse correctly and there are no blank spaces in the workflow form.

RHDHBUGS-3293

Before this update, Developer Lightspeed for RHDH guide was not a part of the in Quickstart steps.

With this release, the guide is featured in the Quickstart steps.

RHDHBUGS-3370

Before this update, the lightspeed-core sidecar container crashed with a PermissionError when writing to the /rag-content/vector_db/notebooks directory. Because Developer Lightspeed for RHDH is enabled by default, this issue caused a CrashLoopBackOff status that blocked all Helm deployments in Amazon Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS) environments.

With this release, container permissions are corrected for non-OpenShift Container Platform (OCP) Kubernetes environments, which lets EKS and AKS Helm deployments start successfully.

RHDHBUGS-3371

Before this update, Orchestrator Loki backend module would fail validation and crash on boot if logPipelineFilters in app-config-yaml file contained brace characters { and } (standard LogQL text template syntax). This caused the local configuration validator to intercept the string value and reject the opening brace character.

With this release, correctly formatted LogQL values are accepted by the validator.

RHDHBUGS-3398

Before this update, the Operator could crash with OutOfMemory errors after running for several hours due to a bloated informer cache holding managedFields for all watched Kubernetes resources.

With this release, managedFields are stripped from the informer cache to reduce memory usage.

RHDHBUGS-3414

Before this update, there was an issue affecting the upgrade of an existing RHDH Helm release from version 1.9 to version 1.10. If you performed an in-place Helm upgrade of an existing Orchestrator-enabled release, the following error message appeared:

Error: UPGRADE FAILED: Job.batch "<release>-create-sonataflow-database" is invalid:

spec.template: Invalid value: ...: field is immutable

With this release, the issue has been fixed.

RHDHBUGS-3439

Lightspeed Core Service has been updated to version 0.5.2 to fix multiple CVEs.

RHIDP-14724

Before this update, the Operator referenced an outdated retrieval-augmented generation (RAG) content image with incorrect labels. This caused a manifest unknown error and led to installation failures. With this update, the Operator references the corrected RAG content image, which resolves the error and ensures a successful installation.

RHDHBUGS-3344

Before this update, grid layout was broken when the quick-access panel was shown.

This release introduced container-query-based responsiveness and added scroll support to prevent content overflow in homepage sections.

RHDHBUGS-1940

Before this update, organizations using Keycloak 26.4.0 or later could see only the top-level groups in the Software Catalog. Nested subgroups were missing after catalog refresh.

With this update, the full group hierarchy including nested subgroups is imported as expected.

RHDHBUGS-2309

Before this update, the zoom and view control buttons in the Topology toolbar were displaying hardcoded English text instead of localized strings across all supported languages.

With this release, these labels, originating from PatternFly, are properly translated.

RHDHBUGS-2405

Before this update, user-provided values referenced deprecated 'janus-idp' templates, causing a conflict with renamed 'rhdh' templates in Helm Chart.

With this release, deprecated 'janus-idp' Helm template references have been replaced with 'rhdh' template references.

RHDHBUGS-2557

Previously, when you switched RHDH to a non-English language such as French, Italian or Japanese, the Notifications page title and left-side navigation menu item would remain in English.

With this update, the page title and navigation menu appear in the selected language.

RHDHBUGS-2585

Before this update, it wasn’t possible to configure dynamic-plugins.yaml to ignore includes defined in default-config/dynamic-plugins.yaml.

With this release, default dynamic plugins can be excluded by sending empty "includes" filed to dynamic-plugins ConfigMap:

dynamic-plugins.yaml: |
    includes: []

RHDHBUGS-2603

This update provides documentation for connecting RHDH to external PostgreSQL databases managed outside the Operator.

For more information, see Configure Orchestrator to connect to existing PostgreSQL infrastructure.

RHDHBUGS-2625

When mirroring plugins for RHDH, the mirror-plugins.sh script no longer needs to rebuild the plugin catalog index image after adjusting image references.

Instead, you should mount a custom registries.conf file into the RHDH init container to transparently mirror the catalog index image and plugins. This approach simplifies the mirroring workflow, and lets you customize the registries.conf for your target mirror registry as needed.

RHDHBUGS-2649

Before this update, rgdg-local would use deprecated backend.auth.keys.

With this release, the deprecated keys were removed and replaced by a static token.

RHDHBUGS-2686

When the Quick Start panel is open, the Developer Lightspeed for RHDH chatbot opens underneath the drawer panel in the overlay display mode. As a consequence, the chatbot interface is obscured.

No known workaround exists.

RHDHBUGS-2701

With this update, documentation for defaultEnvironment parameters and secrets usage is available in RHDH.

For more information, see Default environment parameters and secrets.

RHDHBUGS-2702

Before this update, the chat content in Developer Lightspeed for RHDH overlay mode was not scrollable when it exceeded the container height. Additionally, fixed width caused an unnecessary horizontal scrollbar.

With this release, the overlay mode is responsive to browser window size and vertically scrollable from the beginning of the conversation.

RHDHBUGS-2703

Before this update, incorrect indentation of the additionalImages field in the ImageSetConfiguration manifest generated by the prepare-restricted-environment.sh script caused a conversion error when trying to mirror images using oc-mirror.

With this release, the indentation of additionalImages in the ImageSetConfiguration object has been fixed and calls to oc-mirror work correctly.

RHDHBUGS-2752

Before this update, event created_at values were sometimes stored in the database in non-UTC formats and the frontend could not parse API date strings that used a short timezone offset. This led to inconsistent data and broken date handling in the UI.

With this update, event timestamps are stored in UTC format and frontend date parsing errors in Adoption Insights were fixed.

RHDHBUGS-2826

Previously, the field content of fields marked with ui:hidden was hidden but the surrounding layout (grid spacing and margins) could still show. As a result, the form seemed to have extra space.

With this update, the visual issue is corrected.

RHDHBUGS-2830

With this update, multi-step workflow forms only validate fields on the active step, reducing unnecessary validation calls for hidden steps.

RHDHBUGS-2832

Before this update, the Lightspeed plugin did not display the Tool Call and Thinking sections when used with newer Llama Stack versions, even though the MCP tool responses remained accurate. With this update, the Lightspeed plugin displays the Tool Call and Thinking information correctly.

RHDHBUGS-2855

Before this update, the Deployed status condition on the Backstage CR always reported status: "False", even when the deployment was healthy and the reason was Deployed.

As a consequence, users monitoring the CR status received incorrect information about the deployment state. With this update, the Operator sets the Deployed condition to status: "True" when the Backstage deployment is running successfully. As a result, the CR status conditions accurately reflect the actual deployment state.

RHDHBUGS-2867

Before this update, taking heap dumps with the RHDH must-gather tool (Developer Preview) could be stuck and ultimately time out. The root cause of this issue was that during heap dump collection, the pod could automatically be restarted due to probe failures. This is because the Node.js event loop was paused and for large heaps (1GB+), this could take several seconds, during which the application wouldn’t respond to requests and would end up failing its livenessProbe and therefore automatically restarted by the cluster.

With this release, a different method was implemented for collecting heap dumps and showing regular progress information while the operation is ongoing.

RHDHBUGS-2869

Before this update, workflow form fields with JSON Schema default values were not applied to the form’s initial state. As a consequence, early validation or API calls could fail.

With this update, the initial form state includes JSON Schema default values, preventing early validation and API call failures.

RHDHBUGS-2887

Previously, when using the spec.deployment.patch field in the Backstage CR to inject custom init containers, new items were always appended after the existing default ones. This meant the built-in install-dynamic-plugins init container always ran first, preventing use cases such as running authentication or bootstrap steps before plugin installation.

With this update, you can control the ordering of list items (such as init containers) by setting the rhdh.redhat.com/deployment-patch-list-merge-mode annotation on the Backstage CR to prepend. In prepend mode, you can specify the exact ordering by listing all items (including existing ones) in the desired order in the patch.

For example, to run a custom init container before install-dynamic-plugins and another one after it:

apiVersion: rhdh.redhat.com/v1alpha5
kind: Backstage
metadata:
  name: my-rhdh
  annotations:
    rhdh.redhat.com/deployment-patch-list-merge-mode: prepend
spec:
  deployment:
    patch:
      spec:
        template:
          spec:
            initContainers:
              - name: pre-init
                 image: busybox
                 command: ["sh", "-c", "echo pre-init"]
              - name: install-dynamic-plugins
              - name: post-init
                 image: busybox
                 command: ["sh", "-c", "echo post-init"]

The resulting init container order is: pre-init, install-dynamic-plugins then post-init.

RHDHBUGS-2900

Before this update, the SchemaUpdater applied updates to the root instead of the triggering section. This caused user’s schema updates to incorrectly affect previous sections in the Orchestrator plugin, leading to inconsistencies.

With this release, the SchemaUpdater has been updated to improve handling for nested paths and array-based schemas. Schema updates are applied correctly to the triggering object.

RHDHBUGS-2920

Before this update, the My Groups sidebar submenu was hidden behind the global header, which led to layout and visibility issues.

With this update, the position of the MyGroupSidebarItem has been adjusted to respect the header height. As a result, the vertical layout issue was fixed and My Groups sidebar submenu is visible.

RHDHBUGS-2935

Before this update, sidebar color customization incorrectly affected plugin UI backgrounds due to component targeting issues. As a consequence, sidebar color customization caused plugin UI backgrounds to match, affecting usability.

With this update, the sidebar background color no longer affects custom plugin UI backgrounds.

RHDHBUGS-2981

This update provides clearer instructions for private repository authentication and correct Helm secret name format in third-party plugin installation examples.

The changes include steps for logging in to image registries and clarifying secret names for Helm-based deployments.

RHDHBUGS-474

Before this update, 'app.support.items' was missing from the list of prerequisites for the Support button to appear in the global header.

With this release, the prerequisites include 'app.support.items' in addition to 'app.support.url`. With this, the Support button appears correctly.

RHDHBUGS-686

Before this update, using Operator for air-gapped plugin installation was unsuccessful due to an omission in the installation procedure.

With this release, the installation instructions for air-gapped plugins have been updated to include steps for Operator.

RHDHBUGS-758

With this update, Quick Access card reference has been added to the documentation.

RHDHBUGS-829