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

[Bug]: Terraform apply quits while destroying aws_redshiftserverless_workgroup due to unexpected resource state #28109

Closed
meetvasu15 opened this issue Nov 30, 2022 · 4 comments · Fixed by #28114
Labels
bug Addresses a defect in current functionality. service/redshiftserverless Issues and PRs that pertain to the redshiftserverless service.
Milestone

Comments

@meetvasu15
Copy link

meetvasu15 commented Nov 30, 2022

Terraform Core Version

1.1.5

AWS Provider Version

4.31.0

Affected Resource(s)

  • aws_redshiftserverless_workgroup

Expected Behavior

Terraform destroy stage should wait for for aws to finish destroying aws_redshiftserverless_workgroup even when state is set to "MODIFYING" by aws.

Actual Behavior

Terraform destroy fails when state of the workgroup changes to "MODIFYING".

Relevant Error/Panic Output Snippet

aws_redshiftserverless_workgroup.xxxxx: Destroying... [id=xxxxx]
aws_redshiftserverless_workgroup.xxxxx: Still destroying... [id=xxxxx, 10s elapsed]
aws_redshiftserverless_workgroup.xxxxx: Still destroying... [id=xxxxx, 20s elapsed]
aws_redshiftserverless_workgroup.xxxxx: Still destroying... [id=xxxxx, 30s elapsed]
aws_redshiftserverless_workgroup.xxxxx: Still destroying... [id=xxxxx, 40s elapsed]
aws_redshiftserverless_workgroup.xxxxx: Still destroying... [id=xxxxx, 50s elapsed]
╷
│ Error: error waiting for Redshift Serverless Workgroup (xxxxx) delete: unexpected state 'MODIFYING', wanted target ''. last error: %!s(<nil>)
│
│
╵

Terraform Configuration Files

resource "aws_redshiftserverless_workgroup" "xxxxx" {
namespace_name = aws_redshiftserverless_namespace.eng-datamart-namespace.id
workgroup_name = "xxxxx"
base_capacity = 32
publicly_accessible = false
subnet_ids = data.terraform_remote_state.vpc.outputs.module_vpc_private_subnets
}

Steps to Reproduce

terraform destroy

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No response

@meetvasu15 meetvasu15 added bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Nov 30, 2022
@github-actions github-actions bot added the service/redshiftserverless Issues and PRs that pertain to the redshiftserverless service. label Nov 30, 2022
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Nov 30, 2022
@DrFaust92
Copy link
Collaborator

mm.. maybe some internal op at the same time, ill add modifying to list of states to wait for on destroy

@github-actions
Copy link

github-actions bot commented Dec 2, 2022

This functionality has been released in v4.45.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Jan 2, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2023
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. service/redshiftserverless Issues and PRs that pertain to the redshiftserverless service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants