Display init container error message

[cugykw]

Expected Behavior

When an error occurs in the init container in the pod associated with taskrun, the error message can be clearly displayed.

Actual Behavior

An error occurred in the init container injected by webhook, causing the pod to end. TaskRun
status shows a message build failed for unspecified reasons.

taskrun status:

status:
  completionTime: "2022-10-17T02:04:35Z"
  conditions:
  - lastTransitionTime: "2022-10-17T02:04:35Z"
    message: build failed for unspecified reasons.
    reason: Failed
    status: "False"
    type: Succeeded

pod status:

status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2022-10-17T02:04:30Z"
    message: 'containers with unready status: [xxx]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2022-10-17T02:04:30Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - image: xxx
    imageID: ""
    lastState: {}
    name: xxx
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  initContainerStatuses:
  - containerID: docker://xxx
    image: xxx
    imageID: docker-pullable://xxx
    lastState: {}
    name: xxx
    ready: false
    restartCount: 0
    state:
      terminated:
        containerID: docker://xxx
        exitCode: 1
        finishedAt: "2022-10-17T02:04:34Z"
        reason: Error
        startedAt: "2022-10-17T02:04:34Z"
  phase: Failed

Steps to Reproduce the Problem

1.Inject a failing init container into the pod associated with taskrun.

Additional Info

• Kubernetes version:

kubernetes: 1.21.3

• Tekton Pipeline version:

pipeline version: 0.37.3

[cugykw]

/assign @cugykw

[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.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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 with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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.

[AeroNotix]

I'm having this issue and I can't figure out how to resolve it, sometimes my jobs fail because something happened in the init container steps and the only output I get is "build failed for unspecified reasons".

Is this fixed in fewer issues or is there a workaround?

[afrittoli]

@AeroNotix I'm sorry to hear you're experiencing this issue.
This issue was closed by our bot because it was old and had no activity on it for a long time.
Which version of Tekton are you using? If you're experiencing this feel free to reopen the issue and share more details if applicable.

[AeroNotix]

Using v0.33.2.

Aware this isn't the absolute latest but I want to avoid just blindly updating things unless I know it is actually going to improve any thing.

[afrittoli]

Sure, I understand. Do you have a reproducer for the issue that could be tried on a more recent version, to check if the issue still exists? We would not be able to produce a fix for that version, but if the issue still exists, it could be fixed on a newer version. See which versions we support: https://github.com/tektoncd/pipeline/blob/main/releases.md

[AeroNotix]

I don't particularly have a task spec that I can hand that will reproduce this but the job runs successfully 999 times out of 1000, except when we attempt to launch several tasks concurrently. Typically this task is ran on-demand by humans however we have automation which launches this same task with varying parameters without human intervention. For whatever reason it is only these tasks which fail, when attempting to launch the task again manually with the exact same parameters - it fails with the above error.