Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-6960

Pipelinerun is shown as cancelling in the Openshift Console

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      If pipelinerun spec has status reason CancelledRunFinally
      and pipelinerun has few finally tasks, if any finally task gets
      failed then pipelinerun status showing as Cancelling on the
      console UI, now it is fixed and show as cancelled.
      Show
      If pipelinerun spec has status reason CancelledRunFinally and pipelinerun has few finally tasks, if any finally task gets failed then pipelinerun status showing as Cancelling on the console UI, now it is fixed and show as cancelled.
    • ODC Sprint 3274, ODC Sprint 3275, ODC Sprint 3276, Pipelines Sprint Crookshank 34, Pipelines Sprint Crookshank 35

      Description of problem:

      Pipelinerun is shown as cancelling in the Openshift Console although all taskruns have completed or stopped.

      Prerequisites (if any, like setup, operators/versions):

      OCP: 4.15.36
      openshift-pipelines-operator 1.16

      Steps to Reproduce

      1. Create a pipeline .
      2. Start the pipeline and stop the pipeline the pipelinerun goes into cancelling state as checked from the Web console

      Actual results:

      Pipelinrun is showing cancelling state. 

      Expected results:

      Pipelinerun should show cancelled state or Failed or Succeeded state. 

      Reproducibility (Always/Intermittent/Only Once):

      Intermittent

      Additional info (Such as Logs, Screenshots, etc):

      It has been observed for some of the pipelineruns in clients ENV where the pipelineruns goes into cancelling state.

      This seems to be UI issue. I can see that status should be failed and stopped.

              shverma Shiv Verma
              rhn-support-dtambat Darshan Tambat
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: