Open RoryDoherty opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.
This is still an issue
The relevant code is in https://github.com/argoproj/argo-workflows/blob/master/workflow/util/util.go#L804
Would anyone like to submit a PR to fix this?
Thanks for pointing me in the right direction, I'll take a stab at this next week if I get a chance :+1:
@terrytangyuan I've managed to update the code in FormulateRetryWorkflow to return a workflow with successful dependencies removed from the dag and this works well with unit tests
However I'm now running into an issue buildLocalScopeFromTask specifically on this line https://github.com/argoproj/argo-workflows/blob/master/workflow/controller/dag.go#L588 where because some of the subsequent tasks have completed and the initial dependent task is not available yet the workflow fails to be submitted Would you have any ideas of how to get around this? In FormulateRetryWorkflow is there a way of telling the step to run again without removing it?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.
This is not stale, I just need some guidance
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Not stale, need help in how to proceed
We are also experiencing a similar issue using steps.
@terrytangyuan I've managed to update the code in FormulateRetryWorkflow to return a workflow with successful dependencies removed from the dag and this works well with unit tests
However I'm now running into an issue buildLocalScopeFromTask specifically on this line https://github.com/argoproj/argo-workflows/blob/master/workflow/controller/dag.go#L588 where because some of the subsequent tasks have completed and the initial dependent task is not available yet the workflow fails to be submitted Would you have any ideas of how to get around this? In FormulateRetryWorkflow is there a way of telling the step to run again without removing it?
--
Can you send a link to your code? I'd like to take a look and help if I can. Thanks
@wesleyscholl I've just pushed my local code to here https://github.com/RoryDoherty/argo-workflows/tree/fix-retry-dag
The code requires a rebase but there are conflicts which I haven't time right now to resolve but it should give you an idea of what I was attempting
Pre-requisites
:latest
What happened/what you expected to happen?
If you have an argo workflow dag with the following:
In the event of everything passing except for step C I may want to only retry this step. However if I click Retry on the UI then it will only re run the C step which will obviously fail again as the infrastructure does not exist that step A sets up even though in the dag I have specified dependsOn A Also the OnExit steps will not run again in the event of a retry, is there a way to specify that these should always run even during a retry? More info can be found here https://github.com/argoproj/argo-workflows/discussions/7534
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