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

[Tracker bug] M2K stuck in Active after finishing Q&A

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:
      When executing a move2kube workflow, after completing the Q&A by answering all the questions, the Q&A window closes and a "transfomation completed" notification pop up appears in the Move2kube UI, the workflow never completes execution and the following error appears in the  move2kube pod logs:

      time="2024-08-22T08:16:09Z" level=info msg="failed to fetch the stderr of move2kube transform. Error: \"EOF\""
      time="2024-08-22T08:16:09Z" level=debug msg="Closing transformCh: false"
      time="2024-08-22T08:16:09Z" level=debug msg="ctx not closed"
      time="2024-08-22T08:16:09Z" level=trace msg="checkErr start"
      time="2024-08-22T08:16:09Z" level=debug msg="net.Error: \"Get \\\"http://localhost:41895/problems/current\\\": dial tcp [::1]:41895: connect: connection refused\""
      time="2024-08-22T08:16:09Z" level=debug msg="default *url.Error Get \"http://localhost:41895/problems/current\": dial tcp [::1]:41895: connect: connection refused"
      time="2024-08-22T08:16:09Z" level=trace msg="checkErr end" 

      This appears to be a Move2Kube API issue as from the logs it seems that the pod is looking for another question after all the questions have already been answered. The transformation completes and is done, but then the failure above appears.

      How reproducible: 100%

      Steps to reproduce:

      1. Deploy m2k workflow using chart move2kube-0.3.14, orchestrator 1.2.0-rc,1

      2. Execute the workflow and answer Q&A

      Actual results: Workflow is stuck in Active state, never completes, no notification is generated. 

      Expected results: Workflow should complete normally.

            rh-ee-gfarache Gabriel Farache
            yfirst Yona First
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: