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

Running workflow can't be aborted after deleting the workflow pod

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem: 
      After deleting the pod of a workflow that has running instances, trying to abort the instance after the workflow pod has been deleted and come up again results in a 500 error.

      How reproducible: 100%

      Steps to reproduce:

      1. Deploy with Orchestrator chart 0.2.4

      2. Deploy a workflow, and while it is running, go to the cluster and delete the workflow pod (or scale the deployment to 0)

      3. Wait for the pod to come up, and try to abort the running workflow.

      Actual results: 
      Aborting the workflow fails with 500 error. The workflow remains in Active state forever.

      Expected results:
      Aborting the workflow should succeed. 

        1. backstage-logs.txt
          28.10 MB
        2. di-logs.txt
          24 kB
        3. image-2024-03-20-17-26-23-606.png
          image-2024-03-20-17-26-23-606.png
          115 kB
        4. image-2024-04-02-14-31-54-492.png
          image-2024-04-02-14-31-54-492.png
          157 kB

              gcaponet Guilherme Caponetto
              yfirst Yona First
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: