You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that deleting an aws.ec2.Vpc resource can take a long time if this resource was tied to an IPAM pool.
This behavior is inherited from upstream. IN hashicorp/terraform-provider-aws#30795 specifically commit 563fe2548e7bb32060aa0d91a1be91f6cdb65655 code is introduced to wait for IPAM to remove allocations before considering the VPC to be deleted. This can take a long time. The original timeout was set at 20min. IT has since been updated to 30min.
Perhaps more surprisingly, setting an explicit customTimeout in Pulumi is not helping to short-circuit the deletion.
CLI
Version 3.124.0
Go Version go1.22.5
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.48.0
resource awsx 2.13.0
resource docker 4.5.5
resource docker 3.6.1
language nodejs unknown
Host
OS darwin
Version 14.5
Arch arm64
This project is written in nodejs: executable='/Users/anton/bin/node' version='v18.18.2'
Current Stack: anton-pulumi-corp/slow-vpc-delete/dev
Found no resources associated with dev
Found no pending operations associated with dev
Backend
Name pulumi.com
URL https://app.pulumi.com/anton-pulumi-corp
User anton-pulumi-corp
Organizations anton-pulumi-corp, moolumi, demo, pulumi
Token type personal
Dependencies:
NAME VERSION
@types/node 18.19.43
typescript 5.5.4
@pulumi/aws 6.48.0
@pulumi/awsx 2.13.0
@pulumi/pulumi 3.128.0
Pulumi locates its logs in /var/folders/gd/3ncjb1lj5ljgk8xl5ssn_gvc0000gn/T/com.apple.shortcuts.mac-helper// by default
Additional context
N/A
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).
The text was updated successfully, but these errors were encountered:
This is to avoid the tests failing due to the token expiring.
Newly introduced IPAM-based tests are long running due to a known issue with slow deletions of aws.ec2.Vpc, see
pulumi/pulumi-aws#4346
t0yv0
changed the title
Deleting an aws.ec2.Vpc associated with an IPAM Pool can take a long time
Deleting an aws.ec2.Vpc associated with an IPAM Pool can take 25min
Aug 6, 2024
This is to avoid the tests failing due to the token expiring.
Newly introduced IPAM-based tests are long running due to a known issue
with slow deletions of aws.ec2.Vpc, see
pulumi/pulumi-aws#4346
Describe what happened
It appears that deleting an aws.ec2.Vpc resource can take a long time if this resource was tied to an IPAM pool.
This behavior is inherited from upstream. IN hashicorp/terraform-provider-aws#30795 specifically commit 563fe2548e7bb32060aa0d91a1be91f6cdb65655 code is introduced to wait for IPAM to remove allocations before considering the VPC to be deleted. This can take a long time. The original timeout was set at 20min. IT has since been updated to 30min.
Perhaps more surprisingly, setting an explicit customTimeout in Pulumi is not helping to short-circuit the deletion.
Sample program
Using this program:
IPAM was configured with:
Log output
The relevant bits are:
Affected Resource(s)
aws.ec2.Vpc
Output of
pulumi about
Additional context
N/A
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).
The text was updated successfully, but these errors were encountered: