-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
tests/provider: Removing Default VPC Default Subnets Breaks Certain Testing #13260
Comments
Related:
I hadn't thought of the case of a default VPC without default subnets when I added I should probably tighten that up for the cases where we are explicitly testing launching an instance without specifying a subnet ID. |
A good approach here would be to make those tests that aren't explicitly testing default VPC or EC2-Classic related functionality hermetic and create a VPC and associated resources as part of the test. |
There are also cases where there are default subnets but no default Internet Gateway:
|
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
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. |
Community Note
Description
When the EC2 Default Subnet for an availability zone is deleted, certain acceptance testing is not able to pass. In general, resource acceptance testing should not rely on the Default VPC and Default Subnets except in certain explicit test cases (such as tests for EC2-Classic and Default VPC behavior) since they are a shared resource.
Workaround
A quick fix is recreating the EC2 Default Subnet in the availability zone and applying it to the various default subnet groups for other AWS services:
Tests Affected
The text was updated successfully, but these errors were encountered: