You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the docs, I have the following Example of using the ExitCode in a Retry Expression like this asInt(lastRetry.exitCode). This doesn't work under Windows because the exit code always is 64 with the message Error (exit code 64): exit with non-zero code. exit-code: 3, error:<nil>",
I would expect to be able to use expressions like this in Windows, for which the ExitCode would have to be correctly propagated there as well.
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
# Only retry if the retryStrategy.expression condition is satisfied. In this example, retries will be made until a pod has# exit code 2 or the limit of 10 is reached, whichever happens first.apiVersion: argoproj.io/v1alpha1kind: Workflowmetadata:
generateName: retry-script-spec:
entrypoint: maintemplates:
- name: mainsteps:
- - name: retrytemplate: retry-script
- name: retry-scriptretryStrategy:
limit: "5"# Only continue retrying if the last exit code is greater than 1expression: "asInt(lastRetry.exitCode) > 1"nodeSelector:
kubernetes.io/os: windowscontainer:
image: mcr.microsoft.com/windows-cssc/python3.7.2windows:ltsc2019command: ["python", "-c", "import random; import sys; exit_code = random.choice([1, 2, 3]);sys.exit(exit_code)"]
Pre-requisites
:latest
What happened/what you expected to happen?
From the docs, I have the following Example of using the ExitCode in a Retry Expression like this
asInt(lastRetry.exitCode)
. This doesn't work under Windows because the exit code always is 64 with the messageError (exit code 64): exit with non-zero code. exit-code: 3, error:<nil>",
I would expect to be able to use expressions like this in Windows, for which the ExitCode would have to be correctly propagated there as well.
This is how the workflow looks like:
And later when it's done:
And here is some log output of the main containers:
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: