Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-5504

pipeline with finally tasks status is improper

XMLWordPrintable

    • ODC Sprint 197
    • High

      Description of problem:

      • When users run pipeline with finally task, status looks improper, It says some tasks got cancelled but actually none was.

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

      • OCP 4.7, pipelines 1.3 (p->0.19.0, t->0.10.2)

      Steps to Reproduce

      1. oc create -f https://raw.githubusercontent.com/tektoncd/pipeline/v0.19.0/examples/v1beta1/pipelineruns/pipelinerun-with-final-tasks.yaml

      Actual results:

      Expected results:

      oc describe pipelinerun <write-and-cleanup-workspace>
      Events:
        Type     Reason   Age    From         Message
        ----     ------   ----   ----         -------
        Normal   Started  8m54s  PipelineRun  
        Normal   Running  8m54s  PipelineRun  Tasks Completed: 0 (Failed: 0, Cancelled 0), Incomplete: 2, Skipped: 0
        Normal   Running  8m24s  PipelineRun  Tasks Completed: 1 (Failed: 1, Cancelled 0), Incomplete: 1, Skipped: 0
        Warning  Failed   7m54s  PipelineRun  Tasks Completed: 2 (Failed: 1, Cancelled 0), Skipped: 0
      --------------------------------------------------------------------------
      tkn pr describe           
      ? Select pipelinerun: write-and-cleanup-workspace started 4 minutes ago
      Name:              write-and-cleanup-workspace
      Namespace:         pthangad
      Pipeline Ref:      clone-cleanup-workspace
      Service Account:   default
      Timeout:           1h0m0s
      Labels:
       tekton.dev/pipeline=clone-cleanup-workspace
        Status
      STARTED         DURATION   STATUS
      4 minutes ago   1 minute   Failed
      Message
      Tasks Completed: 2 (Failed: 1, Cancelled 0), Skipped: 0 ("step-clone" exited with code 1 (image: "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init@sha256:20651bc35e950413a5298e925e5900d4c2409c24f077e41389612c2e8fe1be8c"); for logs run: kubectl -n pthangad logs write-and-cleanup-workspace-clone-app-repo-7296j-pod-9cbjh -c step-clone
      )
      Resources
       No resources
      ⚓ Params
       No params
      Results
       No results
      Workspaces
       NAME           SUB PATH   WORKSPACE BINDING
       ∙ git-source   ---        VolumeClaimTemplate
       Taskruns
       NAME                                                 TASK NAME        STARTED         DURATION     STATUS
       ∙ write-and-cleanup-workspace-cleanup-cqlst          cleanup          4 minutes ago   30 seconds   Succeeded
       ∙ write-and-cleanup-workspace-clone-app-repo-7296j   clone-app-repo   4 minutes ago   30 seconds   Failed
      

      Seems none got cancelled, but ideally finally runs by default it shouldn't be skipped or cancelled.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info:

      Providing slack discussion to know more about this bug.

            mdsaud Mohammed Saud (Inactive)
            pthangad Praveen Kumar Reddy Thangadancha (Inactive)
            Gajanan More Gajanan More (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: