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

When running MTA workflow, workflows still running after many hours

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      When deploying the MTA workflow on the backstage instance on my cluster, the workflows continue to run for many hours, using different repos as the source. 

      How reproducible:
      100%

      Steps to reproduce:

      1. Deploy the RHDH orchestrator via Helm chart v 0.1.15 on a OCP cluster deployed on baremetal VMs on a hypervisor

      2. Deploy the MTA workflow via instructions found here

      3. Run the MTA workflow on a repo of your choice

      Actual results: The workflows continue running after many hours.In the orchestrator UI, they appear as in Running or Active state.
      In the MTA UI, the two workflows that have been running for hours appear as FAILED and have not generated a report.   ** 

      Expected results: Workflows should complete running, or fail with an error after a certain amount of time has passed.

      Additional information:

      Screenshot of Orchestrator UI:
       

      Screenshot of MTA UI: 

        1. image-2024-01-11-12-26-09-951.png
          69 kB
          Yona First
        2. image-2024-01-11-12-27-41-067.png
          144 kB
          Yona First
        3. mta-hub-logs.txt
          3.75 MB
          Yona First

            masayag@redhat.com Moti Asayag
            yfirst Yona First
            Yona First Yona First
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: