Deletion of the LB should wait until the underlying network interface as well as the associated EIPs to that interface are deleted / disassociated before reporting deletion success back to Terraform.
Actual Behavior
The assumption here is that deletion of the LB reports as successful even if the underlying network interface and it's EIP associations have not yet been deployed. Terraform goes on with the deletion of resources until the EIP, where it errors, as the EIP has not yet been disassociated.
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.
Terraform Core Version
1.5.6
AWS Provider Version
5.17.0
Affected Resource(s)
Expected Behavior
Deletion of the LB should wait until the underlying network interface as well as the associated EIPs to that interface are deleted / disassociated before reporting deletion success back to Terraform.
Actual Behavior
The assumption here is that deletion of the LB reports as successful even if the underlying network interface and it's EIP associations have not yet been deployed. Terraform goes on with the deletion of resources until the EIP, where it errors, as the EIP has not yet been disassociated.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Debug Output
LB Deletion:
EIP Deletion:
Panic Output
No response
Important Factoids
References
No response
Would you like to implement a fix?
No