-
Notifications
You must be signed in to change notification settings - Fork 341
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
Issues arising from InsufficientInstanceCapacity on aws region eu-west-1 #814
Comments
Related #795 both involve the logic in the subnet selection portion of TPI @ivyleavedtoadflax TPI does make a this is a quick list I put together before:
Also, error logging is another example of #806 |
Thanks @dacbd that's helpful |
Should Close with the release of iterative/terraform-provider-iterative#323 |
These aren't particularly CML issues per-se but it would be good to surface a discussion about them.
Recently when i try to spawn a GPU instance via CML in AWS region eu-west-1 I get the following error:
Ok, all well and good, this is nothing particularly to do with CML, but is it possible though following the advise ☝️ to set the availability zone manually (afaik its only possible to set the region at the moment)?
The second issue is that when i run into this issue when request a spot instance I get the following error:
CancelSpotInstanceRequests, https response error StatusCode: 403, RequestID: 94aa8f89-628c-4d79-98aa-3c009154f184, api error UnauthorizedOperation: You are not authorized to perform this operation.
As I understand it here: CML is waiting ten minute for an instance to be available, once that fails, it tries to remove the Spot request, which fails because in this case it doesn't have permissions. Was there any update to #429 as a reference for permissions, perhaps this needs to include
ec2CancelSpotInstanceRequests
?The text was updated successfully, but these errors were encountered: