Bug #14710

[Workbench] Child containers run on federated clusters do not show up

Added by Peter Amstutz 13 days ago. Updated 13 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Child containers are determined by querying for container requests where requested_by_container_uuid matches the parent container. This does not work for federated workflows, because (a) containers run on remote clusters don't set requested_by_container_uuid and (b) even if it was set, we don't have an easy way to query it (requires either #14374 or generalizing javascript multi-site search feature).

For (a) The arvados-cwl-runner does know which containers it is tracking. so it could explicitly update the container record with a list of child containers, similar to the runtime_status feature.

History

#1 Updated by Peter Amstutz 13 days ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 13 days ago

  • Description updated (diff)

#3 Updated by Tom Morris 13 days ago

  • Status changed from In Progress to New

Also available in: Atom PDF