-
|
How does flyte (console) populate the error message? For some task executions, the error messages are correctly extracted from container logs. But I found some strange case recently where it doesn’t. [1/1] currentAttempt done. Last Error: UNKNOWN: :Outputs not generated by task execution |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Each plugin decides how the second case should be handled. Here is an example: https://github.com/flyteorg/flyteplugins/blob/master/go/tasks/plugins/k8s/container/container.go#L48 Once the error document is written, it exits cleanly, which may result in a discrepancy between the container state and the pod state. |
Beta Was this translation helpful? Give feedback.
The error message is partially Flytekit's responsibility to populate correctly. It uses a protocol to communicate it back to Flytepropeller. This is written using the ErrorDocument.
In the case when Flytekit cannot write an error response - Flytepropeller parses the termination log OR constructs the error (from image pull failure, etc.) using this block determines the error message.
Each plugin decides how the second case should be handled. Here is an example: https://github.com/flyteorg/flyteplugins/blob/master/go/tasks/plugins/k8s/container/container.go#L48
Once the error document is written, it exits cleanly, which may result in a discrepancy between the container state and the p…