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

cannot launch instance on South America (EC2) #314

Closed
luizkowalski opened this issue Mar 30, 2017 · 2 comments
Closed

cannot launch instance on South America (EC2) #314

luizkowalski opened this issue Mar 30, 2017 · 2 comments
Assignees

Comments

@luizkowalski
Copy link

OS / Environment

MacOS 10.12.4

Ansible version

ansible 2.2.0.0

Version of components from requirements.txt

Not sure how to do it...

Summary of the problem

I see this error message when trying to launch an instance on sa-east-1

TASK [cloud-ec2 : Launch instance] *********************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Instance creation failed => Unsupported: Your requested instance type (t2.micro) is not supported in your requested Availability Zone (sa-east-1b). Please retry your request by not specifying an Availability Zone or choosing sa-east-1a, sa-east-1c."}

PLAY RECAP *********************************************************************
localhost                  : ok=11   changed=0    unreachable=0    failed=1

Steps to reproduce the behavior

Just try to launch an instance on EC2 (Sao Paulo)

The way of deployment (cloud or local)

Cloud

@dguido
Copy link
Member

dguido commented Apr 1, 2017

Can you submit a PR to remove that region? I want add a comment in the source code that it doesn't support the size instance we use.

@luizkowalski
Copy link
Author

actually, when I opened the issue was because I would still like to use it on South America region...I thought that changing the AZ to one listed in the logs (or choosing sa-east-1a, sa-east-1c) would be fine. Am I wrong?

faf0 pushed a commit to faf0/algo that referenced this issue Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants