Bug #17257
closed
acrContainerImage not being honored consistently
100%
Description
When using Workbench 2 to create a container request from pirca-7fd4e-c2bb0z0szqdacyc the acrContainerImage field is honored.
When creating a container request from pirca-7fd4e-zkvu363nlkykwu6 it does not honor acrContainerImage, it creates the CR with arvados/jobs.
The only substantive difference I can find is that the 1st on takes a string input, the 2nd one takes a File input which has a default value.
It is particularly odd because the "Runner" field in the "Advanced" section of the form has the correct value. Somehow it is being replaced with the default "arvados/jobs" value before the container request is constructed.
Updated by Peter Amstutz about 4 years ago
Going to the "Workflows" panel and then clicking "Run" on a workflow followed a slightly different code path than going to "+NEW" and "Run a process". This needed to call getWorkflowRunnerSettings() to initialize the "advanced" fields correctly.
17257-wf-advanced-settings @ arvados-workbench2|eb618fd2317411f11d40230e140e60917342a0a9
Updated by Peter Amstutz about 4 years ago
- Status changed from New to In Progress
Updated by Lucas Di Pentima about 4 years ago
Just one nit:
- I think we could un-export the constant at
src/store/run-process-panel/run-process-panel-actions.tsLine 189 now that it isn't used anywhere else.
Otherwise LGTM, thanks!
Updated by Peter Amstutz about 4 years ago
- Status changed from In Progress to Resolved