Flyte node timeout is an usererror (flyteorg#114)

* Flyte node timeout is an usererror * Update executor.go
eapolinario · Apr 16, 2020 · 7028ee3 · 7028ee3
1 parent 7ba3e89
commit 7028ee3
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/pkg/controller/nodes/executor.go b/pkg/controller/nodes/executor.go
@@ -229,7 +229,8 @@ func (c *nodeExecutor) execute(ctx context.Context, h handler.Node, nCtx *nodeEx
 		}
 		if c.isTimeoutExpired(nodeStatus.GetLastAttemptStartedAt(), executionDeadline) {
 			logger.Errorf(ctx, "Current execution for the node timed out; timeout configured: %v", executionDeadline)
-			phase = handler.PhaseInfoRetryableFailure("TimeoutExpired", fmt.Sprintf("task execution timeout [%s] expired", executionDeadline.String()), nil)
+			executionErr := &core.ExecutionError{Code: "TimeoutExpired", Message: fmt.Sprintf("task execution timeout [%s] expired", executionDeadline.String()), Kind: core.ExecutionError_USER}
+			phase = handler.PhaseInfoRetryableFailureErr(executionErr, nil)
 		}
 	}