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

Unable to create a cluster in AWS us-west1 region #1209

Closed
danehans opened this issue Feb 7, 2019 · 1 comment
Closed

Unable to create a cluster in AWS us-west1 region #1209

danehans opened this issue Feb 7, 2019 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. platform/aws

Comments

@danehans
Copy link
Contributor

danehans commented Feb 7, 2019

Version

# Issue is present in both of the following versions:
$ openshift-install version
openshift-install v0.12.0
$ bin/openshift-install version
bin/openshift-install unreleased-master-248-g08afe7edc9729494966b4a43804e44a96a464803

Platform (aws|libvirt|openstack):

aws

What happened?

I run the create cluster command and I expect a cluster to be created. Instead I get:

INFO Creating cluster...                          *****************************************************************************************************************ERROR                                              ****************************************************************************************************************ERROR Error: Error applying plan:                  
ERROR                                              
ERROR 2 errors occurred:                           
ERROR 	* module.vpc.aws_subnet.worker_subnet[0]: 1 error occurred: 
ERROR 	* aws_subnet.worker_subnet.0: Error creating subnet: InvalidParameterValue: Value (us-west-1a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-west-1c, us-west-1b. 
ERROR 	status code: 400, request id: 224016d1-34fb-4c2a-aa22-ac10c8aadda6 
ERROR                                              
ERROR                                              
ERROR 	* module.vpc.aws_subnet.master_subnet[0]: 1 error occurred: 
ERROR 	* aws_subnet.master_subnet.0: Error creating subnet: InvalidParameterValue: Value (us-west-1a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-west-1c, us-west-1b. 
ERROR 	status code: 400, request id: 5c1db52a-fce0-4bb1-b79c-4c3eae8c2de0 
ERROR                                              
ERROR                                              
ERROR                                              
ERROR                                              
ERROR                                              
ERROR Terraform does not automatically rollback in the face of errors. 
ERROR Instead, your Terraform state file has been partially updated with 
ERROR any resources that successfully completed. Please address the error 
ERROR above and apply again to incrementally change your infrastructure. 
ERROR                                              
ERROR                                              
FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply using Terraform

Install log:

...
time="2019-02-07T15:06:11-08:00" level=error msg="Error: Error applying plan:"
time="2019-02-07T15:06:11-08:00" level=error
time="2019-02-07T15:06:11-08:00" level=error msg="2 errors occurred:"
time="2019-02-07T15:06:11-08:00" level=error msg="\t* module.vpc.aws_subnet.worker_subnet[0]: 1 error occurred:"
time="2019-02-07T15:06:11-08:00" level=error msg="\t* aws_subnet.worker_subnet.0: Error creating subnet: InvalidParameterValue: Value (us-west-1a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-west-1c, us-west-1b."
time="2019-02-07T15:06:11-08:00" level=error msg="\tstatus code: 400, request id: 224016d1-34fb-4c2a-aa22-ac10c8aadda6"
time="2019-02-07T15:06:11-08:00" level=error
time="2019-02-07T15:06:11-08:00" level=error
time="2019-02-07T15:06:11-08:00" level=error msg="\t* module.vpc.aws_subnet.master_subnet[0]: 1 error occurred:"
time="2019-02-07T15:06:11-08:00" level=error msg="\t* aws_subnet.master_subnet.0: Error creating subnet: InvalidParameterValue: Value (us-west-1a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-west-1c, us-west-1b."
time="2019-02-07T15:06:11-08:00" level=error msg="\tstatus code: 400, request id: 5c1db52a-fce0-4bb1-b79c-4c3eae8c2de0"
...

What you expected to happen?

A cluster to be created.

How to reproduce it (as minimally and precisely as possible)?

  1. Install the openshift-installer bin (either version as described above).
  2. Setup Route53 DNS
  3. Make sure your AWS config uses us-west-1:
    $ cat ~/.aws/config
    [default]
    output = json
    region = us-west-1
    
  4. Run openshift-install create cluster and observe the error as described above.

Anything else we need to know?

The install fails because us-west-1a does not support the VPC "subnets" feature. According to the AWS Install Guide, "Nodes are spread equally across 3 availability zones.", which makes deploying to the us-west-1 region impossible.

References

@wking
Copy link
Member

wking commented Feb 7, 2019

Ah, yeah, us-west-1a is only for some accounts. We're close to generating those zones from Go, which will make it easier for us to adjust this dynamically. But we still need available-ness filtering in Go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. platform/aws
Projects
None yet
Development

No branches or pull requests

2 participants