fabric-testbed / fabfed

FABRIC Tool-based Federation Kit for a Testbed of Testbeds
MIT License
3 stars 0 forks source link

AWS Direct Connection Takes Too Long to Teardown #112

Closed zlion closed 6 months ago

zlion commented 8 months ago

"fabfed -destroy" failed because it took > 20 min to teardown the VGW.

This is an known AWS issue.

2024-03-08 20:19:10,379 [aws_utils.py:299] [INFO] Detaching vpn:id=vgw-0341b37b57ebc9b5c
2024-03-08 20:19:10,839 [aws_utils.py:305] [WARNING] failed to detach vpn: An error occurred (InvalidParameterValue) when calling the DetachVpnGateway operation: This call cannot be completed because there is a conflicting pending workflow for vgw-0341b37b57ebc9b5c
2024-03-08 20:19:11,151 [aws_utils.py:322] [INFO] Waiting on detached vpn state=attached
2024-03-08 20:19:31,312 [aws_utils.py:322] [INFO] Waiting on detached vpn state=attached
...
2024-03-08 20:39:22,280 [controller.py:413] [WARNING] Exception occurred while deleting resource: Timed out on detaching vpn_gateway: state=attached using aws_provider@aws
2024-03-08 20:39:22,281 [controller.py:391] [WARNING] Skipping deleting resource: fabric_network@network with fabric_provider@fabric
2024-03-08 20:39:22,281 [controller.py:405] [WARNING] Skipping deleting fabric resource: fabric_node@node with fabric_provider@fabric
2024-03-08 20:39:22,281 [fabfed.py:217] [ERROR] Exceptions while deleting resources ...Number Of Exceptions=1:[
msg=Timed out on detaching vpn_gateway: state=attached
]
2024-03-08 20:39:22,282 [fabfed.py:226] [INFO] STATS:provider=aws_provider@aws, provider_duration=Duration(duration=1316.1565339565277, comment='Total time spent in provider')
2024-03-08 20:39:22,282 [fabfed.py:226] [INFO] STATS:provider=fabric_provider@fabric, provider_duration=Duration(duration=0.0055370330810546875, comment='Total time spent in provider')
2024-03-08 20:39:22,312 [fabfed.py:254] [INFO] STATS:duration_in_seconds=Duration(duration=1316.2229471206665, comment='total time spent in destroying workflow')
xi-yang commented 7 months ago

Is this a UX problem or system error? What should be the expectation for an "alternative"?