Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1044

The plugin fails to load workflows if one of the workflows isn't responsive

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Critical

      Description of the problem:

      When one of the workflow isn't responsible (e.g. its pod is down), the plugins attempts to connect to it and fails with 500 or 504, which causes the rest of the workflows not to be shown in the tab.

      How reproducible:

      Always

      Steps to reproduce:

      1. Deploy a workflow successfully

      2. Scale the workflow deployment to 0

      3. Select the Orchestrator on the side panel

      Actual results:

      The plugin fails to load the workflow with 504.

      Expected results:

      The plugin should be able to present the available workflows.

              gcaponet Guilherme Caponetto
              rh-ee-masayag Moti Asayag
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: