When we promote a new bundle to Production, queued Deadline jobs still have the old AYON_BUNDLE_NAME baked into their environment from submission time and fail on publish.
Is there any existing script or recommended workflow to bulk-update AYON_BUNDLE_NAME on all pending/suspended jobs without resubmitting?
We’re considering writing a small Deadline Python API script to iterate jobs and patch the env var, but wanted to check if this is already solved somewhere in the ecosystem before reinventing the wheel. If not, it might be worth a feature request to have GlobalJobPreLoad resolve the bundle dynamically at job start time rather than baking it at submission.
Admittedly it couldn’t (or shouldn’t?) because the bundle itself is the entry point
The older bundle jobs should still continue to work just fine. What’s the urgency with having jobs on Deadline auto-update their bundle name? I’d rather have my deadline jobs come through consistently in the way they were submitted than suddenly (by default) come through with newer AYON updates, etc. applied because it may affect behavior.
Are you getting errors with those existing jobs? If so, what errors?
From my memory (last bundle up), It said something about an Api error in the publish job as it couldn’t, reach the Api which the link of the Api had the old name of the bundle and when I changed and requeued it worked perfectly, that is why I ask before bundling up again soon.
I’ve had a similar error before, but only if the old bundle was archived or deleted. Otherwise it should’ve worked fine. Would be good if you can provide the full render log if you face it again so we can figure out what’s going on.
