You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been seeing an issue in executor-k8s verify function where sometimes it returns an undefined value of the message. When this happens, it is counted as success and there will be no retry even when pod is not starting up, we have seen this in the case of pod unable to start due to bad image.
What you expected to happen:
The message should not be undefined, it should throw an error when pod is not in a running condition to allow retry.
How to reproduce it:
Spin up some build with bad node and monitor the logs.
The text was updated successfully, but these errors were encountered:
What happened:
We have been seeing an issue in executor-k8s verify function where sometimes it returns an
undefined
value of the message. When this happens, it is counted as success and there will be no retry even when pod is not starting up, we have seen this in the case of pod unable to start due to bad image.What you expected to happen:
The message should not be undefined, it should throw an error when pod is not in a running condition to allow retry.
How to reproduce it:
Spin up some build with bad node and monitor the logs.
The text was updated successfully, but these errors were encountered: