Uploaded image for project: 'Red Hat Developer Hub Bugs'
  1. Red Hat Developer Hub Bugs
  2. RHDHBUGS-2527

RHDH with Orchestrator won't start with 1.9 Helm or Operator

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      = Existing Operator users with Orchestator 1.7 or 1.8 require a manual update in their dynamic-plugins ConfigMap

      If you have an existing Operator-backed instance of {product-short} with the Orchestrator, you must update your dynamic-plugins ConfigMap once the {product-short} Operator is upgraded to 1.9.
      Otherwise, the {product-short} instance will not be upgraded at all.

      .Example of a dynamic-plugins ConfigMap enabling the Orchestrator plugins in 1.9 for Operator-backed instances
      [source,yaml,subs='+attributes,+quotes']
      ----
      apiVersion: v1
      kind: ConfigMap
      metadata:
        name: dynamic-plugins-rhdh
      data:
        dynamic-plugins.yaml: |
          includes:
            - dynamic-plugins.default.yaml
          plugins:
            - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator:{{inherit}}'
              disabled: false
            - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:{{inherit}}'
              disabled: false
              dependencies:
                - ref: sonataflow
            - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:{{inherit}}'
              disabled: false
            - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:{{inherit}}'
              disabled: false
      ----
      Show
      = Existing Operator users with Orchestator 1.7 or 1.8 require a manual update in their dynamic-plugins ConfigMap If you have an existing Operator-backed instance of {product-short} with the Orchestrator, you must update your dynamic-plugins ConfigMap once the {product-short} Operator is upgraded to 1.9. Otherwise, the {product-short} instance will not be upgraded at all. .Example of a dynamic-plugins ConfigMap enabling the Orchestrator plugins in 1.9 for Operator-backed instances [source,yaml,subs='+attributes,+quotes'] ---- apiVersion: v1 kind: ConfigMap metadata:   name: dynamic-plugins-rhdh data:   dynamic-plugins.yaml: |     includes:       - dynamic-plugins.default.yaml     plugins:       - package: ' oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator: {{inherit}}'         disabled: false       - package: ' oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend: {{inherit}}'         disabled: false         dependencies:           - ref: sonataflow       - package: ' oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator: {{inherit}}'         disabled: false       - package: ' oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets: {{inherit}}'         disabled: false ----
    • Removed Functionality
    • RHDH Install 3286, RHDH Install 3287

      Description of problem:

      Issue caught in the rhdh-chart nightly checks (which run against the quay.io/rhdh-community/rhdh:next RHDH image): https://github.com/redhat-developer/rhdh-chart/actions/runs/21152188069/job/60830283759

      Prerequisites (if any, like setup, operators/versions):

      Helm or Operator from the upstream main branches or from the downstream `next` tags.

      Steps to Reproduce

      Follow the docs to deploy either Helm or Operator-based instances of RHDH with the Orchestrator plugins enabled.

      Actual results:

      Readiness probe fails with the following error in the logs:

      2026-01-19T20:55:56.348Z catalog info Registered scheduled task: PluginInstallStatusProcessor:refresh-packages, {"version":2,"cadence":"PT30M","initialDelayDuration":"PT10S","timeoutAfterDuration":"PT10M"} task="PluginInstallStatusProcessor:refresh-packages"
2026-01-19T20:55:56.541Z backstage error Plugin 'scaffolder' threw an error during startup, waiting for 15 other plugins to finish before shutting down the process. Cannot read properties of undefined (reading 'id') type="initialization" stack="TypeError: Cannot read properties of undefined (reading 'id')\n    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackendInitializer.cjs.js:262:72\n    at Array.map (<anonymous>)\n    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackendInitializer.cjs.js:262:59\n    at Array.map (<anonymous>)\n    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackendInitializer.cjs.js:256:35\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async Promise.allSettled (index 4)\n    at async #doStart (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackendInitializer.cjs.js:242:21)\n    at async BackendInitializer.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackendInitializer.cjs.js:160:5)\n    at async BackstageBackend.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/wiring/BackstageBackend.cjs.js:19:5)"
2026-01-19T20:55:56.973Z events info Database is PostgreSQL, using database store
[...]
2026-01-19T21:18:32.550Z rootHttpRouter info [2026-01-19T21:18:32.549Z] "GET /.backstage/health/v1/liveness HTTP/1.1" 200 15 "-" "kube-probe/1.33" type="incomingRequest" date="2026-01-19T21:18:32.549Z" method="GET" url="/.backstage/health/v1/liveness" status=200 httpVersion="1.1" userAgent="kube-probe/1.33" contentLength=15 trace_id="0662b788f73ca73bbeb2cc9f13ba8cb4" span_id="ae918b696ce9082d" trace_flags="01"
2026-01-19T21:18:39.818Z rootHttpRouter info [2026-01-19T21:18:39.818Z] "GET /.backstage/health/v1/readiness HTTP/1.1" 503 58 "-" "kube-probe/1.33" type="incomingRequest" date="2026-01-19T21:18:39.818Z" method="GET" url="/.backstage/health/v1/readiness" status=503 httpVersion="1.1" userAgent="kube-probe/1.33" contentLength=58 trace_id="e1cd26575e4810ce4b5751e9d893399b" span_id="12e080f7d89da409" trace_flags="01"

      Expected results:

      Should start correctly. Looks like we need to change the versions of the Orchestrator plugins to make sure they are compatible with the version of Backstage used in RHDH 1.9.

      We might need to switch to the OCI versions of the Orchestrator plugins.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

              rh-ee-lahern Leanne Ahern
              rh-ee-asoro Armel Soro
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: