Replies: 2 comments
-
I think it is another cause because OOM confirms that it is retried. metadata:
name: lovely-rhino1
namespace: pr-90616-workflow-secure
labels:
example: 'true'
spec:
arguments:
parameters:
- name: message
value: hello argo
entrypoint: argosay
templates:
- name: argosay
retryStrategy:
limit: 2
retryPolicy: Always
inputs:
parameters:
- name: message
value: '{{workflow.parameters.message}}'
container:
name: main
image: argoproj/argosay:v2
command:
- /argosay
args:
- echo
- '{{inputs.parameters.message}}'
resources:
limits:
memory: 8Mi
requests:
memory: 8Mi
ttlStrategy:
secondsAfterCompletion: 300
podGC:
strategy: OnPodCompletion |
Beta Was this translation helpful? Give feedback.
0 replies
-
argo-workflows/workflow/controller/operator.go Lines 990 to 1007 in 3bb637c |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Basically, retries work as set up.
However, the retry did not work only for the attached Workflow.
I don't know the cause of the problem, and I couldn't decide whether I should report it as a bug or not.
If you check the manifest file, you will see that the following retry settings are made in main.
But there appears to be only aya-jobs-import-webdm-tp5wx-881703283 as a child of aya-jobs-import-webdm-tp5wx in node.
What is happening?
If it is a bug, can you please check it for us to isolate it since we don't know what the condition is?
manifest
aya-jobs-import-webdm-tp5wx.txt
workflow-controller
workflow-controller.txt
workflow
Beta Was this translation helpful? Give feedback.
All reactions