-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
DigitalOcean : Region is not available. #941
Comments
Since ansible 2.5 we can move the prompts to the playbook. It would be more elegant way to ask user for any input. Covered here |
That would effectively be way more elegant than the bash script, besides being awesome. Thanks ! |
Some possibly related weirdness when selecting a DO region:
Given these regions via the script:
I've queried the regions using v2 of the DO API (abridged) which may relate to which regions are actually available:
|
OS / Environment (where do you run Algo on)
Cloud Provider (where do you deploy Algo to)
Summary of the problem
The selected region is not available.
The reason is surely the following :
DigitalOcean displays an unavailability for this datacenter, when connected on their interface.
"Due to limited availability we have temporarily disabled droplet creation in this region."
This is not really an Algo bug, but it would come handy if in the future Algo would only present datacenters that are actually available (e.g. by doing a first request with the given API token, and then listing the regions in reply).
I guess the same applies for the other providers, too.
Steps to reproduce the behavior
Launch algo with Digital Ocean selection, then choose "1" (Amsterdam (Datacenter 2)), and continue.
Full log
The text was updated successfully, but these errors were encountered: