Bug #14710

Updated by Peter Amstutz 4 months ago

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.


# Add a @child_requests@ field to @container@ which has an array (array or jsonb type) of container request uuids
# In @controller@, when handling a @container_request@ create from a container, update @child_requests@
# Workbench displays @child_requests@ instead of searching on @requested_by_container_uuid@
# API server should use @child_requests@ for priority propagation (?)