We had a block allocation for an image that is limited to 4 concurrent sessions. When the allocation time arrived, users who were in the user group for the allocation trying to make a reservation received a message stating that the environment is limited in the number of concurrent sessions, and that no further reservations could be made during this time. There were NO active reservations for the image at the time.
By increasing the concurrent limit on the image, these users were then able to make a reservation. I verified that the users were indeed in the user group. It was if it wasn't honoring their group membership for the allocation, although when I increased the limit and they successfully made a reservation, I could see that they were getting the reserved machines. Why wouldn't it allow any reservations for a block allocation that matched the concurrent use limit?? Mike Waldron Systems Specialist ITS - Research Computing Center University of North Carolina at Chapel Hill
