Timeout during the creation of internal elb

[frederic-boissiere]

Hi there,

Terraform Version

$ terraform --version
Terraform v0.12.9
+ provider.flexibleengine v1.8.0

Affected Resource(s)

• flexibleengine_elb_loadbalancer

Terraform Configuration Files

data "flexibleengine_vpc_v1" "private_vpc" {
  name = "private_vpc"
}

data "flexibleengine_networking_secgroup_v2" "ams_sg" {
  name        = "ams_sg"
}

#LOAD BALANCER
resource "flexibleengine_elb_loadbalancer" "elb_ams" {
  name              = "elb_ams"
  type              = "Internal"
  admin_state_up    = true
  vpc_id            = "${data.flexibleengine_vpc_v1.private_vpc.id}"
  vip_subnet_id     = "${data.flexibleengine_vpc_subnet_v1.private_vpc_subnet_v1_eu_west_0a.id}"
  az                = "eu-west-0a"
  security_group_id = "${data.flexibleengine_networking_secgroup_v2.ams_sg.id}"
}

Debug Output

DEBUG.log

Panic Output

N/A

Expected Behavior

Creation of Internal ELB must be successfully completed

Actual Behavior

A timeout occurred whereas the ELB is visible in the flexible engine console :

Steps to Reproduce

$ terraform plan --out=plan.out
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

....
------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # flexibleengine_elb_loadbalancer.elb_ams will be created
  + resource "flexibleengine_elb_loadbalancer" "elb_ams" {
      + admin_state_up    = true
      + az                = "eu-west-0a"
      + id                = (known after apply)
      + name              = "elb_ams"
      + region            = (known after apply)
      + security_group_id = "036332fe-d25d-4c94-89fe-93ce2f06feff"
      + tenantid          = (known after apply)
      + type              = "Internal"
      + vip_address       = (known after apply)
      + vip_subnet_id     = "dc15af55-8f05-47ac-861b-8bf76a4ccea4"
      + vpc_id            = "eda478e0-9374-414d-8482-bb7f27c3c8b8"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

This plan was saved to: plan.out

To perform exactly these actions, run the following command to apply:
    terraform apply "plan.out"

bvzq1484@EB-PC0EWL55 MINGW64 /c/travail/PSA/infra/terraform/4_access_management_servers (feature/ams_cluster)
$ terraform apply "plan.out"
flexibleengine_elb_loadbalancer.elb_ams: Creating...
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [10s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [20s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [30s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [40s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [50s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [1m0s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [1m10s elapsed]
...
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [9m56s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [10m9s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [10m21s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [10m34s elapsed]
flexibleengine_elb_loadbalancer.elb_ams: Still creating... [10m46s elapsed]

Error: A timeout occurred

  on elb.tf line 10, in resource "flexibleengine_elb_loadbalancer" "elb_ams":
  10: resource "flexibleengine_elb_loadbalancer" "elb_ams" {

Important Factoids

N/A

References

N/A

[antonin-a]

@niuzhenguo did you manage to reproduce ?

[niuzhenguo]

@antonin-a @frederic-boissiere Actually it exceeded our default create timeout 10 mins on terraform side. Not sure why it took so long time on cloud side but you can avoid this by manually setting a timeout on your tf scripts.

[antonin-a]

@niuzhenguo @frederic-boissiere can we close this one ? Are you still facing this issue ?

[frederic-boissiere]

hello @antonin-a, you can close it. I no longer use flexibleengine_elb_loadbalancer