AWS ELB creation fails: timeout while waiting for state to baecome '[success]'

[anosulchik]

Hi, I'm using 0.6.12 to create set of aws resources including ELB. It's never created and fails with the following error:

1 error(s) occurred:

* aws_elb.service_elb: timeout while waiting for state to become '[success]'

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.

Here's ELB's definition:

resource "aws_elb" "service_elb" {
  name = "tf-${var.service_name}-${var.environment_name}"
  subnets = ["${split(",", lookup(var.subnet_ids, var.availability_zones))}"]
  security_groups = [ "${aws_security_group.ecs_security_group.id}" ]
  cross_zone_load_balancing = true
  internal = true
  idle_timeout = 300
  connection_draining = true
  connection_draining_timeout = 120

  listener {
    instance_port = 443
    instance_protocol = "https"
    lb_port = 443
    lb_protocol = "https"
    ssl_certificate_id = "${var.elb_cert_id}"
  }

  health_check {
    healthy_threshold = 3
    unhealthy_threshold = 10
    timeout = 15
    target = "HTTPS:443/manage/health"
    interval = 20
  }
}

Here's what terraform shows when it starts creation of ELB (I've replaced ids of subnets and SGs here):

aws_elb.service_elb: Creating...
  availability_zones.#:                   "" => "<computed>"
  connection_draining:                    "" => "1"
  connection_draining_timeout:            "" => "120"
  cross_zone_load_balancing:              "" => "1"
  dns_name:                               "" => "<computed>"
  health_check.#:                         "" => "1"
  health_check.0.healthy_threshold:       "" => "3"
  health_check.0.interval:                "" => "20"
  health_check.0.target:                  "" => "HTTPS:443/manage/health"
  health_check.0.timeout:                 "" => "15"
  health_check.0.unhealthy_threshold:     "" => "10"
  idle_timeout:                           "" => "300"
  instances.#:                            "" => "<computed>"
  internal:                               "" => "1"
  listener.#:                             "" => "1"
  listener.2040477470.instance_port:      "" => "443"
  listener.2040477470.instance_protocol:  "" => "https"
  listener.2040477470.lb_port:            "" => "443"
  listener.2040477470.lb_protocol:        "" => "https"
  listener.2040477470.ssl_certificate_id: "" => "arn:aws:iam::xxx:server-certificate/wc.stg.xxx.net.2015-11-02"
  name:                                   "" => "tf-myservice-staging"
  security_groups.#:                      "" => "1"
  security_groups.1691032259:             "" => "sg-0000000"
  source_security_group:                  "" => "<computed>"
  source_security_group_id:               "" => "<computed>"
  subnets.#:                              "" => "3"
  subnets.1170323386:                     "" => "subnet-0000000"
  subnets.1403265116:                     "" => "subnet-0000000"
  subnets.2899423186:                     "" => "subnet-0000000"
  zone_id:                                "" => "<computed>"

Please advise. Thank you!

[egarbi]

@anosulchik check the name of certificate. I have seen this error before when I was passing a non-existent SSL cert name

[anosulchik]

thanks @egarbi !

[egarbi]

This is related to #5102

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.