When a user requests a lease for a specific duration (e.g., 6h) and the request is rejected due to availability constraints, the current error message implies that no resources are available at all. However, resources often are available, but only for a shorter window (e.g., 3h) due to scheduling or pool policies.
Current Behavior: User requests a board for 6h. The system returns a generic failure/not found message, even if the board is free for the next 3 hours. The user is left assuming the pool is entirely full.
Proposed Solution: Improve the controller logic to check available time slots upon rejection. If the resource is free now but not for the full requested duration, the error message should explicitly suggest the maximum available lease time.
When a user requests a lease for a specific duration (e.g., 6h) and the request is rejected due to availability constraints, the current error message implies that no resources are available at all. However, resources often are available, but only for a shorter window (e.g., 3h) due to scheduling or pool policies.
Current Behavior: User requests a board for 6h. The system returns a generic failure/not found message, even if the board is free for the next 3 hours. The user is left assuming the pool is entirely full.
Proposed Solution: Improve the controller logic to check available time slots upon rejection. If the resource is free now but not for the full requested duration, the error message should explicitly suggest the maximum available lease time.