We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Python client call to declare file replicas as bad fails silently, without giving any results to the user about success or failure.
The docs https://rucio.github.io/documentation/client_api/replicaclient#declare_bad_file_replicas for the command say that a list of dids for which the declaration failed is returned. However, this does not seem to be the case.
Are there use cases where the silent failing is an intended behaviour?
Use a random scope and name for a file with the command, with a valid RSE
>>> client.declare_bad_file_replicas([{'scope': 'cms', 'name': 'InvalidFileName', 'rse': 'T2_IT_Rome'}], reason='Lost on Disk') {}
No response
The text was updated successfully, but these errors were encountered:
Recovery: Add logging and catch if did does not exist in client output …
3dced90
…rucio#6741
0ebf16a
voetberg
No branches or pull requests
Description
The Python client call to declare file replicas as bad fails silently, without giving any results to the user about success or failure.
The docs https://rucio.github.io/documentation/client_api/replicaclient#declare_bad_file_replicas for the command say that a list of dids for which the declaration failed is returned.
However, this does not seem to be the case.
Are there use cases where the silent failing is an intended behaviour?
Steps to reproduce
Use a random scope and name for a file with the command, with a valid RSE
Rucio Version
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: