Logs of regular taskruns appear after logs of finally tasksruns

[VeereshAradhya]

Versions and Operating System

• Kubernetes version:

  Output of kubectl version:

  Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b3b92b2", GitCommit:"b3b92b2", GitTreeState:"clean", BuildDate:"2020-07-15T09:27:21Z", GoVersion:"go1.14.3", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.3+012b3ec", GitCommit:"012b3ec", GitTreeState:"clean", BuildDate:"2020-07-24T07:23:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
  

• Tekton Pipeline version:

  Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

  $ ./tkn version
  Client version: dev
  Pipeline version: v0.14.3
  Triggers version: v0.6.1
  

• Operating System:

  Linux

Expected Behavior

Logs of regular taskruns should appear before logs of finally taskruns

Actual Behavior

Logs of regular taskruns appear after logs of finally tasksruns

Steps to Reproduce the Problem

1. Create a pipeline run with the spec https://github.com/tektoncd/cli/blob/master/test/resources/pipelinerun-with-finally.yaml
2. Run tkn pr logs -f exit-handler

Additional Info

Command Execution logs

[varadhya@localhost cli]$ cat  cli/test/resources/pipelinerun-with-finally.yaml
# Copyright 2020 The Tekton Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: exit-handler
spec:
  pipelineSpec:
    finally:
      - name: echo-on-exit
        taskSpec:
          steps:
            - args:
                - echo "finally"
              command:
                - sh
                - -c
              image: library/bash:4.4.23
              name: main
    tasks:
      - name: print-msg
        taskSpec:
          steps:
            - args:
                - echo "printing a message"
              command:
                - sh
                - -c
              image: library/bash:4.4.23
              name: main
[varadhya@localhost cli]$ 
[varadhya@localhost cli]$ kubectl apply -f cli/test/resources/pipelinerun-with-finally.yaml
pipelinerun.tekton.dev/exit-handler created
[varadhya@localhost cli]$ 
[varadhya@localhost cli]$ ./tkn pr logs -f exit-handler
[echo-on-exit : main] finally

[print-msg : main] printing a message

Note: It is not reproducible all the times. Need to run steps multiple times to reproduce the issue

[pradeepitm12]

/assign

[vdemeester]

@pradeepitm12 what is the status here ?

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[nikhil-thomas]

/remove-lifecycle rotten looks like this is still valid. this should be fixed as part ofhttps://github.com/tektoncd/cli/pull/1385

[nikhil-thomas]

This could be closed as this is handled in https://github.com/tektoncd/cli/pull/1385

[tekton-robot]

@nikhil-thomas: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/tektoncd/cli/issues/1146#issuecomment-887485720): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[pradeepitm12]

This could be closed as this is handled in #1385

/close

[tekton-robot]

@pradeepitm12: Closing this issue.

In response to [this](https://github.com/tektoncd/cli/issues/1146#issuecomment-887656390): >> This could be closed as this is handled in #1385 > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.