Kubernetes pipelines sometimes don't show step failure output

Hello!

I want to report a bug seen after I’ve converted my docker pipeline to a kubernetes pipeline (I’m using Drone 2).

A step failure (eg. make returning an >0 status code) gets (sometimes) incorrectly reported as the “container failed to start” error. When looking at the output while it runs, you can actually see it switch from the black box with streaming stderr/stdout to the red box in the screenshot below. After the red box replaces the black stdout box, there’s no way to see the actual error.

screenshot_2021-11-17_at_14.52.03

I’ve been working around this issue by removing type: kubernetes from all steps in our dronefile and running again. Builds ran in this way let you see the actual error.

Please let me know what other info I need to provide. Thank you!

2 Likes