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

Orchestrator DB Creation Job should be able to retry properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.9.0
    • 1.8.0, 1.8.1
    • Helm Chart, Orchestrator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Bug Fix
    • RHDH Install 3285

      Description of problem:

      More context in this Slack thread: https://redhat-internal.slack.com/archives/C05HGAR2DT5/p1765212646522309

      The Orchestrator DB creation Job (template) does not retry if it fails (and hides the failures behinds warning messages in the logs), causing subsequent issues that might be difficulit to investigate and troubleshoot.
      https://github.com/redhat-developer/rhdh-chart/blob/release-1.8/charts/backstage/templates/sonataflows.yaml#L85-L196

      Different approaches were discussed in the thread above, which we can investigate:

      • This job could maybe be a cron, so that it eventually works when the root cause of the failure is fixed. Let's check this as well.
      • This job already has a hardcoded backoffLimit set to 2, so it should retry twice at most. But this is not happening because of the `|| echo WARNING...` which make the job look like it succeeded. We can remove this so the job fails accordingly, and we should also make the backoffLimit configurable.

              Unassigned Unassigned
              rh-ee-asoro Armel Soro
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: