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

nerc-project / operations

Issues related to the operation of the NERC OpenShift environment

1 stars 0 forks source link

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

Open Milstein opened 11 months ago

Milstein commented 11 months ago

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 commented 8 months ago

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