Open sidoruka opened 2 years ago
Shall be backported to release/0.16
@sidoruka @mzueva backported to release/0.16
(11feac47f786110fcd04dedaa42620aba7eaba2b)
Case:
Actual results:
Unable to parse CP_CAP_LIMIT_MOUNTS value (1,161) with error: Failed to find storage by its id or name. Error message: Exceeded maximum retry count 3 for API request.
No remote storages are available or CP_CAP_LIMIT_MOUNTS configured to none
No storages can be mounted
[Questions] What behavior is expected in that case? And should be the user-level settings are applied in that case?
Test cases were created by #2253 and located here.
e2e-tests were implemented via #2274.
Daily e2e-tests results are located and updated here (for AWS
).
Background At the moment, Cloud Pipeline allows settings environment variables (and thus
CP_CAP_LIMIT_MOUNTS
) using the following options:launch.env.properties
- globally for all the jobsBut for certain cases - users would benefit from setting default list of mounted storages (e.g. for the
ROLE_ADMIN
).Approach
Profile
section of the settings using the same GUI control as in the Tool/Job parameters:CP_CAP_LIMIT_MOUNTS
with a comma-delimited list of storage IDsLaunch form
- the values from theProfile
shall be applied to theLimit mounts
input automaticallyLaunch form
: if a tool has any limits set, they shall be used. Otherwise - user-level settings are used.CP_CAP_LIMIT_MOUNTS
shall be applied in the following priority order: