-
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
Variables not re-calculated in pod spec patch when re-submitting workflow #8832
Comments
I'm not sure what the semantics should be for "resubmit" vs "resubmit + memoized" should be. See #2320 "memoized" blurs "resubmit" and "retry". I thought that resubmit should nil the status and start again, but that's not what the code does: argo-workflows/workflow/util/util.go Line 672 in d8aa467
I think that loop should only run in Could you like to submit a PR to fix? |
Thanks Alex, was about to tackle this but then I noticed something: argo-workflows/workflow/util/util.go Lines 660 to 662 in d8aa467
Or am I missing something? |
Hmm. You're correct. |
Are you re-submitting with memoized? |
I'm not using memoized anywhere in the workflow that I submit, The demo workflow above also doesn't use it I was just clicking resubmit from the Web UI, do you know if it defaults to memoized? |
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 issue still exists |
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. |
issue still exists |
This issue has been closed due to inactivity. Feel free to re-open if you still encounter this issue. |
This issue still exists |
@alexec Can this be reopened? I'm still seeing this behaviour in v3.4.3 |
Checklist
Summary
What happened/what you expected to happen?
Ran a workflow which uses
{{workflow.name}}
to upload artifacts to a unique locationWorkflow name is stored in an env var in podSpecPatch so that it is available to all pods that are created
I then resubmitted the same workflow and noticed the env var with the workflow name was not updated in the new pod
What version are you running?
v3.3.5
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
If you run the below workflow once and then resubmit it via the UI you will see the issue
Logs from the workflow controller:
Log from first run:
Log from rerun:
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: