search

ClusterHQ / unofficial-flocker-tools

A tool to make installing Flocker with container orchestration tools easier and more fun
https://clusterhq.com/
11 stars 9 forks source link

Terraform installer cannot be used twice in the same region due to security group collisions #31

Closed robhaswell closed 8 years ago

robhaswell commented 8 years ago

I ran the Terraform installer in a location where it had already been run, and received this error:

$ uft-flocker-get-nodes --ubuntu-aws
aws_security_group.cluster_security_group: Creating...
  description:                          "" => "Allow SSH, HTTP, Flocker APIs"
  egress.#:                             "" => "1"
  egress.482069346.cidr_blocks.#:       "" => "1"
  egress.482069346.cidr_blocks.0:       "" => "0.0.0.0/0"
  egress.482069346.from_port:           "" => "0"
  egress.482069346.protocol:            "" => "-1"
  egress.482069346.security_groups.#:   "" => "0"
  egress.482069346.self:                "" => "0"
  egress.482069346.to_port:             "" => "0"
  ingress.#:                            "" => "4"
  ingress.2214680975.cidr_blocks.#:     "" => "1"
  ingress.2214680975.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2214680975.from_port:         "" => "80"
  ingress.2214680975.protocol:          "" => "tcp"
  ingress.2214680975.security_groups.#: "" => "0"
  ingress.2214680975.self:              "" => "0"
  ingress.2214680975.to_port:           "" => "80"
  ingress.2541437006.cidr_blocks.#:     "" => "1"
  ingress.2541437006.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2541437006.from_port:         "" => "22"
  ingress.2541437006.protocol:          "" => "tcp"
  ingress.2541437006.security_groups.#: "" => "0"
  ingress.2541437006.self:              "" => "0"
  ingress.2541437006.to_port:           "" => "22"
  ingress.3049929765.cidr_blocks.#:     "" => "1"
  ingress.3049929765.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.3049929765.from_port:         "" => "4523"
  ingress.3049929765.protocol:          "" => "tcp"
  ingress.3049929765.security_groups.#: "" => "0"
  ingress.3049929765.self:              "" => "0"
  ingress.3049929765.to_port:           "" => "4523"
  ingress.968969066.cidr_blocks.#:      "" => "0"
  ingress.968969066.from_port:          "" => "4524"
  ingress.968969066.protocol:           "" => "tcp"
  ingress.968969066.security_groups.#:  "" => "0"
  ingress.968969066.self:               "" => "1"
  ingress.968969066.to_port:            "" => "4524"
  name:                                 "" => "flocker_rules"
  owner_id:                             "" => "<computed>"
  vpc_id:                               "" => "<computed>"
Error applying plan:

1 error(s) occurred:

* aws_security_group.cluster_security_group: Error creating Security Group: InvalidGroup.Duplicate: The security group 'flocker_rules' already exists for VPC 'vpc-7dbc5a14'
    status code: 400, request id: []

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
lukemarsden commented 8 years ago

this is fixed now; terraform creates a new VPC per cluster.

(it now means you can't have more than 5 clusters per region).