fix panic when trying to read pod logs when pod is already deleted

[divyansh42]

Changes

fixed panic when trying to call log.NewReader(logType, opts) for a pipelineRun, but some of the task pod has been deleted.

Initial work is done in #2411, due to inactivity taking up the follow up changes

/kind bug

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Run the code checkers with make check
• Regenerate the manpages, docs and go formatting with make generated
• Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

fix panic when trying to read pod logs when pod is already deleted

[divyansh42]

/hold

[divyansh42]

/hold cancel

[divyansh42]

/cc @piyush-garg

[pratap0007]

/lgtm

[vinamra28]

Hi @divyansh42, can you please add the steps to reproduce this?

[divyansh42]

Hi @divyansh42, can you please add the steps to reproduce this?

The case that is fixed in the PR is very rare, and I guess this can be reproduced in a very tight scenario where the pod is pruned just after it is received in the podC channel. I have tried to reproduce that, but unfortunately couldn't get it done. Just modified a few more things, like the continue statement and error messages based on my understanding and based on the initial PR from the user.

[vinamra28]

/approve
/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vinamra28

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vinamra28]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment