[BUG]: Quota capacity limit exceeded

[EvgenyUglov]

Bug Description

Testing Provisioning for CSM Authorization Gen 2

Created a initial capacity of 100GB
Pod 1 = 8GB tnb-ocpb-338f52b6f1 8d70aa6400000077 Thin 8 GB
Pod 2 = 16GB tnb-ocpb-0291fb523f 8d70aa6800000079 Thin 16 GB
Pod 3 = Initially 24GB and Expanded by 40GB tnb-ocpb-131f8d36f1 8d70aa6c0000007b Thin 64 GB
Pod 4 = 8 GB - Pending

Total Provisioned = successfully = 88 GB | Remaining 12 GB
Pod 4 should be able to provision as there is enough capacity remaining

Increased Capacity to 104 GB and Pod 4 eventually started successfully.
Rolled Pod 5 with an 8GB volumes and its pending

Deleted all Pods and Volumes
Rolled a Single Pod with 104GB volume - pending

Deleted and Rolled a Single pod with 96 GB volume = success
At first I thought it was related to the fact I did a volume expansion. So I created a new role this time of 1024GB

Updated the token, restarted the controller and driver pods ... provisioned a pod with 512 GB successfully and then expanded to 1024GB and it "took".

Perhaps it was starting with the 100GB quota for the first role used?

Logs

Created a initial capacity of 100GB
Pod 1 = 8GB tnb-ocpb-338f52b6f1 8d70aa6400000077 Thin 8 GB
Pod 2 = 16GB tnb-ocpb-0291fb523f 8d70aa6800000079 Thin 16 GB
Pod 3 = Initially 24GB and Expanded by 40GB tnb-ocpb-131f8d36f1 8d70aa6c0000007b Thin 64 GB
Pod 4 = 8 GB - Pending

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

• Created Role with "100GB" of quota
• Created following volumes:
  • 8GB Success
  • 16GB Success
  • 64GB Success
  • 8GB Failed due to insufficient quota

Expected Behavior

Pod is successful

CSM Driver(s)

N/A

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

N/A

Operating System

N/A

[gallacher]

/sync

[csmbot]

link: 26176