PipelineRun init errors should be displayed in the Tekton Dashboard

[CarolynMabbott]

Expected Behavior

When a pipelinerun fails it should update the pipelinerun properly

Actual Behavior

The pipelinerun fails and is stuck failing without logs as the pod is stuck in initError state
There are no logs to explain why it has failed

Additional Info

Not just applicable to this example, screenshot below

[a-roberts]

I'm wondering if this can be used to remedy #560

[mnuttall]

I'm not sure what's possible here - use this to investigate whether initialisation errors can be reliably detected, and meaningful messages extracted.

[AlanGreene]

We added code to handle some init error cases for #200
This may need to be updated to include additional classes of error that aren't currently handled.

[EnriqueL8]

👍 on this feature

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/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.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

We should do another review to make sure all cases are covered, and only then close this.

/remove-lifecycle rotten
/reopen

[tekton-robot]

@AlanGreene: Reopened this issue.

In response to this:

We should do another review to make sure all cases are covered, and only then close this.

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

I think it would be a good idea to consider this along with #972 and #1445 to ensure we provide a good experience and don't introduce too many different mechanisms for accessing errors / logs.

[AlanGreene]

Since Dashboard v0.7 we now display additional information on the TaskRun status (by selecting the TaskRun in the tree) which will include relevant details for many of these cases.

Once #1814 is merged, init step container details will always be displayed, not just in case of error as they are today. This will address the last remaining problem covered by this issue.

[AlanGreene]

/assign