Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: set daemon pod failed when exit with a non-zero status. Fixes:#12911 #12988

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

shuangkun
Copy link
Member

Fixes #12911

Motivation

set daemon pod failed when exit with a non-zero status

Modifications

Verification

@shuangkun shuangkun force-pushed the fix/DaemonPod branch 2 times, most recently from 2ac9757 to 1724e0b Compare April 27, 2024 17:51
@shuangkun shuangkun marked this pull request as draft April 27, 2024 17:54
@shuangkun shuangkun closed this Apr 27, 2024
@shuangkun shuangkun reopened this Apr 27, 2024
@shuangkun shuangkun force-pushed the fix/DaemonPod branch 3 times, most recently from 91f43b6 to 7dd8b0e Compare May 8, 2024 11:43
@shuangkun
Copy link
Member Author

/retest

Signed-off-by: shuangkun <tsk2013uestc@163.com>
@shuangkun shuangkun marked this pull request as ready for review May 9, 2024 09:34
WithField("pod", pod.Name).Infof("Pod failed: %s", new.Message)
}
new.Phase, new.Message = woc.inferFailedReason(pod, tmpl)
woc.log.WithField("displayName", old.DisplayName).WithField("templateName", old.TemplateName).WithField("pod", pod.Name).Infof("Pod failed: %s", new.Message)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like somebody explicitly thought that Daemons should never been in a Failed state. Do we understand why?

@juliev0
Copy link
Contributor

juliev0 commented May 10, 2024

It appears that this was by design that the Workflow and Node should succeed even if the Daemon failed. I wonder if it should be configurable in the ConfigMap and/or Workflow if perhaps some users want the opposite?

@shuangkun
Copy link
Member Author

It appears that this was by design that the Workflow and Node should succeed even if the Daemon failed. I wonder if it should be configurable in the ConfigMap and/or Workflow if perhaps some users want the opposite?

Yes I can try that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Daemon pod is always succeeded even with a non-zero status code
2 participants