Skip to content
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

Traceback when requesting the global account usage with a specific RSE #4870

Closed
dchristidis opened this issue Sep 28, 2021 · 0 comments · Fixed by #4894
Closed

Traceback when requesting the global account usage with a specific RSE #4870

dchristidis opened this issue Sep 28, 2021 · 0 comments · Fixed by #4894
Assignees

Comments

@dchristidis
Copy link
Contributor

Motivation

As reported to ATLAS DDM Ops:

$ 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

@bari12 bari12 assigned joeldierkes and unassigned maany Oct 6, 2021
joeldierkes pushed a commit to joeldierkes/rucio that referenced this issue Oct 6, 2021
…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.
joeldierkes pushed a commit to joeldierkes/rucio that referenced this issue Oct 6, 2021
…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.
bari12 added a commit that referenced this issue Oct 12, 2021
…equesting_the_global_account_usage_with_a_specific_RSE

Client: Fix faulty list account usage test and untracked error #4870
bari12 pushed a commit that referenced this issue Oct 12, 2021
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.
@bari12 bari12 added this to the 1.26.6-clients milestone Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants