RDS creation often timing out about terraform-provider-aws HOT 8 CLOSED

This comment was originally opened by @catsby as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

Hey @thegedge – thanks for writing in. I'm not sure how best to "solve" this. One idea would be a flag to allow you to simply not wait at all after we get the "creating" status (meaning everything thing we sent over validated and the creation process is underway). Another could be a user supplied int for the timeout.

maybe reset the timeout counter back to zero it if the state changes at all.

What state changes are you imagining here? From my experience it's simply in creating for that whole time, am I missing another step?

from terraform-provider-aws.

This comment was originally opened by @thegedge as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

It usually goes creating --> modifying --> backing up, so for each of those transitions I was thinking we could reset the timeout counter. An integer flag would be great too, especially if .terraformrc supported setting flag defaults for the various commands.

I'm not really into the idea of not waiting because that requires me to go to the AWS console to know everything is completed (not a terrible thing, but it would be nice to avoid this). It also breaks some of our use cases where we use a local-exec provisioner to set up some database users and such.

from terraform-provider-aws.

This comment was originally opened by @catsby as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

creating --> modifying --> backing up

I just tried this out, and went from creating -> available. It's possbily my modifying step was too quick I suppose? The backing up step only happens if the user supplies a value for backup retention (I don't, in my tests..)

I'm not really into the idea of not waiting because that requires me to go to the AWS console

Not waiting is probably not the best solution, but I thought I'd throw it out there...

from terraform-provider-aws.

This comment was originally opened by @thegedge as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

I just tried this out, and went from creating -> available. It's possbily my modifying step was too quick I suppose?

Possibly. We have non-default parameter groups and multi AZ enabled, which seems to constitute some of the "modifying". Not sure of exactly what's happening during the "modifying" phase. The only thing I know is that RDS is painful :)

The simplest solution would definitely be to just have a configurable flag, and I'd be happy with that. Even more so if we could set this flag with a default value via .terraformrc.

from terraform-provider-aws.

This comment was originally opened by @failshell as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

I get plagued by that issue as well.

I never had that issue if I created a multi-AZ masters setup with slaves that had empty databases. That's very quick to do.

I walk into the time out issue when I create slaves from a multi AZ masters setup that have data in it. I'm guessing the snapshot restore + deploy is way over 40 mins. At least in my case.

from terraform-provider-aws.

This comment was originally opened by @scheffield as hashicorp/terraform#2886 (comment). It was migrated here as part of the provider split. The original comment is below.

Any progress on this one? Creating RDS instances from snapshots can take a while. Since hitting the timeout only happens for a very small set of actions I would love to see a parameter --timeout=true|false.

from terraform-provider-aws.

I am going to close this out - RDS instances now support custom timeouts as per the docs

from terraform-provider-aws.

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!

from terraform-provider-aws.