Skip to content

Conversation

@Dhanush010
Copy link

When using @Retry(times=0) with JobSet through Argo Workflows, the workflow fails because {{retries}} is added to the jobset-name even though retryStrategy is not specified in the template.

The issue was that the code checked for the presence of the @Retry decorator instead of checking if retries are actually enabled (total_retries > 0). When total_retries = 0, retry_strategy() doesn't add retryStrategy, so {{retries}} is not available in Argo Workflows.

Fix by computing total_retries and only adding retry-related parameters (including {{retries}} in the jobset-name) when total_retries > 0.

Fixes #2632

When using @Retry(times=0) with JobSet through Argo Workflows, the
workflow fails because {{retries}} is added to the jobset-name even
though retryStrategy is not specified in the template.

The issue was that the code checked for the presence of the @Retry
decorator instead of checking if retries are actually enabled
(total_retries > 0). When total_retries = 0, retry_strategy() doesn't
add retryStrategy, so {{retries}} is not available in Argo Workflows.

Fix by computing total_retries and only adding retry-related parameters
(including {{retries}} in the jobset-name) when total_retries > 0.

Fixes Netflix#2632
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.

Issue when using Jobset with @retry(times=0)

1 participant