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

Add more descriptive output for when no allocations are found #272

Merged
merged 24 commits into from
Nov 12, 2024
Merged

Conversation

Comeani
Copy link
Contributor

@Comeani Comeani commented Nov 11, 2024

This PR should resolve #271 for now. It does not try to figure out what's actually causing the problem, but it's less confusing to users than an IndexError.

The actual solution will be to sync group info from LDAP to keystone if we can.

I also noticed a few instances where CRC needed to be changed to CRCD.

djperrefort and others added 24 commits June 11, 2022 13:28
@Comeani Comeani requested a review from chnixi November 11, 2024 20:44
@Comeani
Copy link
Contributor Author

Comeani commented Nov 11, 2024

@chnixi Is

No allocation information found. Either the group does not have any allocations, or you do not have permissions to view them. If you believe this to be a mistake, please submit a help ticket to the CRCD team.

sufficient for the error message?

@chnixi
Copy link
Contributor

chnixi commented Nov 12, 2024

Yes, that looks good.

@chnixi chnixi merged commit 4c71fd2 into main Nov 12, 2024
11 checks passed
@chnixi chnixi deleted the issue-271 branch November 12, 2024 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better handle crc-usage display when user is not permitted to view output
3 participants