-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Workflows fail when cluster-scoped resources have successCondition #9320
Labels
Comments
Good catch. Would you like to submit a PR to fix this? |
Sure, I'll do that |
@Kyle-Wong can you try to reproduce on 3.3 release? |
I was able to reproduce the issue on 3.3 release. |
Yeah it should still be a problem. Please submit a PR and we'll review. |
terrytangyuan
pushed a commit
that referenced
this issue
Aug 18, 2022
juchaosong
pushed a commit
to juchaosong/argo-workflows
that referenced
this issue
Nov 3, 2022
…9320 (argoproj#9375) Signed-off-by: juchao <[email protected]>
Closed
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Summary
What happened/what you expected to happen?
I expected this workflow to succeed. It applies a namespace and has a successCondition. The resource is applied successfully, but the workflow is marked as failed because of
The resource has been deleted while its status was still being checked. Will not be retried: the server could not find the requested resource
. This is because the selflink for the namespace resource is malformed:SelfLink: api/v1/namespaces//namespaces/kubeflow
. This selflink is used during the evaluation of successConditions. This issue still exists in latest because inferSelfObjectLink doesn't account for cluster-scoped resources. According to kubernetes docs, the correct selflink should be/api/v1/namespaces/kubeflow
What version are you running?
Argo workflows v2.3.11, but the issue still exists in latest version
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: