Clarify what `ignore_availability` flag of add_rule does
Open
@bari12 is already working on this.
Since Mar 18, 2025.
- Dominant language
- Python
- Stars
- 4
- Forks
- 71
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 11
Description
This page [1] explains this flag as Option to ignore the availability of RSEs. I interpreted this as when this flag is provided submitter will submit the transfers to the external transfer tool even if the availability_write of the RSE is False. I learned at [2] this is not the case. Rucio will accept the rule, but will make it immediately STUCK and not submit transfers. This should be clarified in the documentation.
[1] https://rucio.github.io/documentation/html/client_api/ruleclient.html#rucio.client.ruleclient.RuleClient.add_replication_rule
[2] https://github.com/rucio/rucio/issues/4271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.