RDS: Unexpected state 'modifying', wanted target 'available'

[johnwards]

On a fresh build of RDS (That contains a couple of ec2 instances and a ELB) I get the following at the end of the run

aws_db_instance.default: Error: unexpected state 'modifying', wanted target 'available'

The instance is created in AWS, but yes the state is marked as modifying and is like that for a while. Is this a timeout issue?

[pearkes]

This is a configuration issue with our function designed to wait for the DB. Fixed in master, let me know if that doesn't resolve it.

[johnwards]

Hmm so I'm not sure if it was this commit but I've just updated again from master and when running make (after running make updatedeps) I get the following:

ok      github.com/hashicorp/terraform/depgraph 0.019s
--- FAIL: TestWriteDot (0.00 seconds)
    graphviz_test.go:28: bad: digraph {
            "e";
            "a";
            "a" -> "b" [label="foo"];
            "a" -> "c" [label="Edge"];
            "b";
            "b" -> "d" [label="Edge"];
            "b" -> "e" [label="Edge"];
            "c";
            "d";
        }
FAIL
FAIL    github.com/hashicorp/terraform/digraph  0.016s

[pearkes]

@johnwards That's just a test that has order dependency issues (see #53), so you can safely ignore that.

[lzecca78]

Hi guys, i don't know if this is the right place, but i have a identical exception in the resource aws_dms_replication_instance :

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

Terraform version : 0.9.11

[stack72]

Hi @lzecca78

Please can you tell me, was this as part of the creation of aws_dms_replication_instance or as part of updating it?

Thanks

Paul

[lzecca78]

hi @stack72 , i encountered this kind of error every time i create a new aws_dms_replication_instance. As far as i can see, you already merged a fix about this 👍

[stephanlindauer]

@lzecca78 what pr was that?

[davidvuong]

I'm encountering this issue (except my state is storage-optimization) when I try to increase our RDS allocated_storage.

Error: Error applying plan:
1 error(s) occurred:
* module.rds.aws_db_instance.xxx: 1 error(s) occurred:
* aws_db_instance.xxx: unexpected state 'storage-optimization', 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.

I'm running the latest version of Terraform v0.11.0, storage_encrypted=true, storage_type=gp2.

[VikasBains]

Using Terraform v0.10.8

Error: Error applying plan:

1 error(s) occurred:

* aws_db_instance.postgresql_test2: 1 error(s) occurred:

* aws_db_instance.postgresql_test2: timeout while waiting for state to become 'available, storage-optimization' (last state: 'creating', timeout: 40m0s)

Any update?

[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.