You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The srm scheme currently requires space_token as extended_attribute, however when space_token is not set, rucio complains about extended_attributes and web_service_path not specfied.
if ('space_token'notinparameter['extended_attributes']) or ('web_service_path'notinparameter['extended_attributes']):
raiseexception.InvalidObject('Missing values! For SRM, extended_attributes and web_service_path must be specified')
Expected behavior
Ideally , space_token would be an optional attribute, and if not used, no spacetoken should be passed to FTS transfer job submission command. See also #574
The text was updated successfully, but these errors were encountered:
Outside ATLAS (particularly, for CMS), space tokens are optional at
some SRM endpoints. Previously, for rucio#574, we fixed the conveyor
to handle empty space tokens. Additionally, the fix for the client-side
of rucio#575 got mistakenly wrapped up in rucio#570 (pluggable LFN2PFN) and put
into `next`.
This is the missing piece for `master`.
Motivation
The srm scheme currently requires space_token as extended_attribute, however when space_token is not set, rucio complains about extended_attributes and web_service_path not specfied.
Modification
Happens in these lines:
rucio/lib/rucio/core/rse.py
Lines 691 to 692 in 5fa4bb2
Expected behavior
Ideally , space_token would be an optional attribute, and if not used, no spacetoken should be passed to FTS transfer job submission command. See also #574
The text was updated successfully, but these errors were encountered: