-
Notifications
You must be signed in to change notification settings - Fork 7
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
Resources staying in STARTING/DELETING state #134
Labels
Comments
This may happen in two situations:
|
praiskup
changed the title
Resources staying in STARTING state
Resources staying in STARTING/DELETING state
Mar 1, 2024
A similar thing happens when deleting OpenStack instances, from time to time, after (not 100% this is triggering the problem)
|
No, that would be different, I'm not sure what happened, starting of the instance in DELETING state failed:
... probably stayed in STARTING becuase of this bug. Then I restarted resalloc, and it stayed in DELETING state after:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These machines are STARTING for multiple days. The fact that the allocator failed should be detected.
The text was updated successfully, but these errors were encountered: