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

ColdFront Expired/ (Activated and then Denied) resource allocations are still available for users to deploy their workload #268

Open
Milstein opened this issue Oct 13, 2023 · 1 comment

Comments

@Milstein
Copy link

  • This is an issue for both OpenStack and OpenShift based Resource Allocations.
  • What will be the progress flow to properly set this and make user unable to expired allocation. Also need to clean up before we expired the allocation otherwise still in background resources / PI/ projects are going to be costing money!
@QuanMPhm
Copy link

QuanMPhm commented Jan 16, 2024

It seems the problem can be attributed to this bug in Coldfront's backend code. The line is intended to evaluate whether the change made to a allocation was either "Denied" or "Revoked", but used the wrong operator to do so. This meant nothing will happen if the allocation's status was changed to "Denied" or "Revoked".

I've sent a PR to upstream Coldfront here: ubccr/coldfront#596

@Milstein Milstein reopened this May 15, 2024
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

No branches or pull requests

2 participants