Skip to content

aws_dms_replication_instance resource creation has too short of a timeout #1182

Description

@ryan-dyer-sp

Terraform Version

v0.9.11

Affected Resource(s)

Please list the resources as a list, for example:

  • aws_dms_replication_instance

Terraform Configuration Files

resource "aws_dms_replication_instance" "default" {
  allocated_storage = 20
  apply_immediately = true
  replication_instance_class = "${var.repl_instance_size}"
  engine_version = "1.9.0"
  replication_instance_id = "${var.pod_name}-repl-cc"
  publicly_accessible = false
  multi_az = true
  replication_subnet_group_id = "default-${data.aws_vpc.selected.id}"
  vpc_security_group_ids = [ "${data.aws_security_group.db_sg.id}" ]
}

Debug Output

aws_dms_replication_instance.default: Still creating... (3m0s elapsed)
Releasing state lock. This may take a few moments...
Error applying plan:

1 error(s) occurred:

* aws_dms_replication_instance.default: 1 error(s) occurred:

* aws_dms_replication_instance.default: unexpected state 'modifying', wanted target 'available'. last error: %!s(<nil>)

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.
[terragrunt] [/home/rdyer/repos/sp-terraform/providers/dev/cc_db_dms/us-east-1/alcatraz] 2017/07/18 20:30:53 Module /home/rdyer/repos/sp-terraform/providers/dev/cc_db_dms/us-east-1/alcatraz has finished with an error: exit status 1
[terragrunt] 2017/07/18 20:30:53 Encountered the following errors:
exit status 1

Panic Output

-NA-

Expected Behavior

The resource creation should not timeout after 3 mins. A t2.large instance can take much longer to standup and become available. I'd suggest at least a 15 minute timeout. Multiple attempts at creating this resource has put the time to create right around the 10 mark; different instance sizes may take longer.

Actual Behavior

terraform fails. I can wait until the instance does become available and then rerun tf apply to continue the building up remaining infrastructure.

Steps to Reproduce

  1. terraform apply

Important Factoids

-NA

References

-NA

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAddresses a defect in current functionality.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions