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
$ rucio -v list-account-usage --rse TRIUMF-LCG2_SCRATCHDISK desilva
+-------------------------+----------+-----------+--------------+
| RSE | USAGE | LIMIT | QUOTA LEFT |
|-------------------------+----------+-----------+--------------|
| TRIUMF-LCG2_SCRATCHDISK | 1.915 kB | 20.000 TB | 20.000 TB |
+-------------------------+----------+-----------+--------------+
2021-09-23 07:57:52,097 DEBUG rucio Traceback (most recent call last):
File "/opt/atlas/atlasadmin/ATLASLocalRootBase/x86_64/rucio-clients/1.25.5/bin/rucio", line 134, in new_funct
return function(*args, **kwargs)
File "/opt/atlas/atlasadmin/ATLASLocalRootBase/x86_64/rucio-clients/1.25.5/bin/rucio", line 1649, in list_account_usage
if (args.rse and args.rse in item['resolved_rses']) or not args.rse:
KeyError: 'resolved_rses'
2021-09-23 07:57:52,100 ERROR
The object is missing this property: 'resolved_rses'
This should never happen. Please rerun the last command with the "-v" option to gather more information.
Completed in 1.0040 sec.
Note that this is done with a privileged account and, therefore, is not affected by #4838.
Modification
The text was updated successfully, but these errors were encountered:
…4870
When an RSE was specified for the list-account-usage an KeyError:
'resolved_rses' was generated. The key does not exist in the underlying data
model.
The `test_list_account_usage` did not report the problem since the regex, which
compared the actual output with the expected result, contained an unescaped `|`
character. Hence the test produced a passing test, while a failing was expected.
…4870
When an RSE was specified for the list-account-usage an KeyError:
'resolved_rses' was generated. The key does not exist in the underlying data
model.
The `test_list_account_usage` did not report the problem since the regex, which
compared the actual output with the expected result, contained an unescaped `|`
character. Hence the test produced a passing test, while a failing was expected.
When an RSE was specified for the list-account-usage an KeyError:
'resolved_rses' was generated. The key does not exist in the underlying data
model.
The `test_list_account_usage` did not report the problem since the regex, which
compared the actual output with the expected result, contained an unescaped `|`
character. Hence the test produced a passing test, while a failing was expected.
Motivation
As reported to ATLAS DDM Ops:
Note that this is done with a privileged account and, therefore, is not affected by #4838.
Modification
The text was updated successfully, but these errors were encountered: