Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] make cloud reservation lockout expire if cloud naturally expires #534

Open
sadsfae opened this issue Oct 3, 2024 · 0 comments
Open

Comments

@sadsfae
Copy link
Member

sadsfae commented Oct 3, 2024

When you define a new cloud environment a reservation lockout period begins (default is 48hrs), this is designed to reserve this cloud from someone else taking it for scheduling.

When a cloud environment is released and expires within 48hours this is still active, it'd be nice to have cloud expiration also close the cloud define lockout period too.

e.g. cloud02 was provisioned below for only a few hours and then naturally expired but quads --find-free-cloud returns:

cloud02 (reserved: 43hr 37min remaining)
cloud03 (reserved: 47hr 59min remaining)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

1 participant