New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not require space tokens for SRM #574
Comments
Currently Rucio unconditionally passes spacetoken json parameter to FTS job. No matter what value is passed, this causes fts error on CMS sites which do not support spacetokens. |
…pacetokens Conveyor: Handle empty spacetokens correctly. Fix #574
…pacetokens Conveyor: Handle empty spacetokens correctly. Fix #574
Hi @bbockelm , how do I now define an RSE so that it would not pass the spacetoken to FTS? |
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`.
…_tapes update static usage for tape rses
At many CMS sites, space tokens are not used even when SRM is utilized. However, it's not currently possible to skip this setting.
It may be as simple as setting the space token to the empty string (``), which could be done automatically if not specified.
However, there might be hidden dependencies that want a non-empty-string space token. Needs investigation.
The text was updated successfully, but these errors were encountered: