timeout while waiting for state to become 'available'

[sebastianfeduniak]

What happened?

While upgrading Aurora cluster to the newer version (major), pulumi crashes after an hour even that the cluster was available after ~10 mins.

Steps to reproduce

For me, it was just upgrading Aurora cluster (2 nodes: 1 reader, 1 writer) from engine version 13.6 to 14.4.

Expected Behavior

Aurora cluster upgraded without the issues.

Actual Behavior

After ~1 hour, pulumi crashes with the following error:

  aws:rds:Cluster (db-***)
    error: 1 error occurred:
	* updating urn:pulumi:uat::***::aws:rds/cluster:Cluster::db-***: 1 error occurred:
	* error waiting for RDS Cluster (db-***) to be available: timeout while waiting for state to become 'available' (last state: 'upgrading', timeout: 1h0m0s)

Even that the cluster is available and running in ~10 mins.

Output of pulumi about

pulumi v3.42.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[guineveresaenger]

Hi @sebastianfeduniak - thank you for reporting. Can you help us out with a little more detail?

• Which version of the pulumi-aws provider are you using?
• Does the behavior persist on a subsequent run of pulumi up? Specifically, you are seeing behavior where the cluster upgrades just fine on AWS, yet Pulumi times out on you - correct?
• Can you supply us with the code you're using?

I suspect that this is at least somewhat related to upstream behavior

[mikhailshilkov]

The issue looks stale by now. Since we don't have a good repro, I'll go ahead and close it. Please open a new issue with all appropriate details if the problem persists.