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

Feature: Add support for an all-in-one script - failure modes InsufficientInstanceCapacity #15

Open
eformat opened this issue Nov 27, 2022 · 1 comment

Comments

@eformat
Copy link
Owner

eformat commented Nov 27, 2022

as a user, i just want to run one script .. puhlease !!

eformat added a commit that referenced this issue Nov 27, 2022
@eformat
Copy link
Owner Author

eformat commented Nov 28, 2022

failure scenarios - no spot capacity available part way through process

e.g. all instances terminated, ec2 conversion fails with temporary resource issues:

botocore.exceptions.ClientError: An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 5): We currently do not have sufficient m5a.2xlarge capacity in the Availability Zone you requested (ap-southeast-2a). Our system will be working on provisioning additional capacity. You can currently get m5a.2xlarge capacity by not specifying an Availability Zone in your request or choosing ap-southeast-2b, ap-southeast-2c.
An error occurred (InsufficientInstanceCapacity) when calling the StartInstances operation (reached max retries: 2): You can't start the Spot Instance 'i-003bc5e90fbd29150' because there is no available Spot capacity.

to make things fully re-runnable, we would need to search for "terminated" instance(s) and retry the conversion command, or cache it in a .dotfile perhaps and retry n#times until successful.

or (at the least) provide some manual HELP/instructions when this occurs.

@eformat eformat changed the title Feature: Add support for an all-in-one script Feature: Add support for an all-in-one script - failure modes InsufficientInstanceCapacity Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant