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

aws_dms_replication_instance resource creation has too short of a timeout #1182

Closed
ryan-dyer-sp opened this issue Jul 19, 2017 · 7 comments
Closed
Labels
bug Addresses a defect in current functionality.

Comments

@ryan-dyer-sp
Copy link
Contributor

ryan-dyer-sp commented Jul 19, 2017

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

@ryan-dyer-sp
Copy link
Contributor Author

Also of note is that the documentation says it supports the timeouts flag and default for create is 30m. I have also tried to set timeouts for create and I still see terraform bail on creating this resource after 3m and not being in the available state.

@Ninir
Copy link
Contributor

Ninir commented Jul 26, 2017

Hey @ryan-dyer-sp,

It seems related to a AWS missing status, that has been fixed.

Are you able to check using Terraform 0.10 RC1, and the v0.1.3 release for the AWS provider?

Thanks!

@Ninir Ninir added bug Addresses a defect in current functionality. waiting-response Maintainers are waiting on response from community or contributor. labels Jul 26, 2017
@ryan-dyer-sp
Copy link
Contributor Author

If you can point me to a download location, I'd be happy to.

@radeksimko
Copy link
Member

Here's where to get the mentioned RC version of Terraform:
https://releases.hashicorp.com/terraform/0.10.0-rc1/

We (intentionally) don't publish RCs and betas on the website as they don't have the same guarantees of stability. In other words once we reach 0.10.0 final it will be published at https://www.terraform.io/downloads.html as usual.

@stack72
Copy link
Contributor

stack72 commented Aug 9, 2017

@radeksimko / @Ninir now that 0.10 is generally available - should this be closed?

@radeksimko
Copy link
Member

That's right - thanks for the ping @stack72

@ghost
Copy link

ghost commented Apr 11, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
@breathingdust breathingdust removed the waiting-response Maintainers are waiting on response from community or contributor. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

No branches or pull requests

5 participants