Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When an image has a max concurrent usage set and there is a block allocation for that image, the number of nodes in the block allocation count toward the max concurrent usage even without having a reservation for them. Example - image has concurrent usage of 6; block allocation for for image with 6 as the number of seats; no one, including the members of the block allocation, can make a reservation for the image. The fix is to ignore block allocations that the user is a member of when counting up the block allocated nodes for the image.