-
Notifications
You must be signed in to change notification settings - Fork 362
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
Unable to delete the CIDR Block after VPC is deleted #677
Labels
bug
Something isn't working
Comments
Hi @AmnaIrfan! Looks like we need to return with @AmnaIrfan Would you be interested in contributing this fix? |
@muvaf Yes I will be fix this today. Thank you! |
AmnaIrfan
added a commit
to AmnaIrfan/provider-aws
that referenced
this issue
May 28, 2021
Signed-off-by: Amna Irfan <amirfan@ea.com>
AmnaIrfan
added a commit
to AmnaIrfan/provider-aws
that referenced
this issue
Jun 2, 2021
Signed-off-by: Amna Irfan <amirfan@ea.com>
tektondeploy
pushed a commit
to gtn3010/provider-aws
that referenced
this issue
Mar 12, 2024
Enable ESS Plugin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
CIDR blocks are attached to VPCs so deleting a VPC in Crossplane automatically deletes the CIDR block in AWS. However the CIDR resource does not get deleted in Crossplane. The deletion gets stuck in a loop since AWS first tries to get the VPC and when the VPC doesn't exist it sends a VPC not found error while the code is waiting for a CIDR not found error.
We just need to account for the VPC not found error while deleting a CIDR block.
How can we reproduce it?
What environment did it happen in?
Crossplane version:
def0bab
The text was updated successfully, but these errors were encountered: