On the remote TES(K) instances, the tasks are actually completed, so the issue must be in proTES.
Need to figure out details, but one reason may be that the external (TESK) task ID (of the form task- followed by 8-character string composed of numbers and lower-case characters) rather than the proTES task ID (7-character string composed of numbers and upper-case characters) is returned for POST /tasks.
Upgrading the deployment via Helm didn't update the Celery worker image. Manually restarting the pod with the latest image solved the issue. No changes necessary.
On the remote TES(K) instances, the tasks are actually completed, so the issue must be in proTES.
Need to figure out details, but one reason may be that the external (TESK) task ID (of the form
task-
followed by 8-character string composed of numbers and lower-case characters) rather than the proTES task ID (7-character string composed of numbers and upper-case characters) is returned forPOST /tasks
.