-
Notifications
You must be signed in to change notification settings - Fork 343
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
Update ec2_instance.py #652
Update ec2_instance.py #652
Conversation
vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error-> ``` TASK [manage_ec2_instances : Create EC2 instances for ansible node (control node)] ********************************************************************************************************** fatal: [localhost]: FAILED! => changed=false msg: No default subnet could be found - you must include a VPC subnet ID (vpc_subnet_id parameter) to create an instance ``` changing to match other examples
Build failed.
|
recheck |
Build succeeded.
|
Build succeeded (gate pipeline).
|
Backport to stable-2: 💚 backport PR created✅ Backport PR branch: Backported as #653 🤖 @patchback |
Update ec2_instance.py SUMMARY vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error-> TASK [manage_ec2_instances : Create EC2 instances for ansible node (control node)] ********************************************************************************************************** fatal: [localhost]: FAILED! => changed=false msg: No default subnet could be found - you must include a VPC subnet ID (vpc_subnet_id parameter) to create an instance changing to match other examples ISSUE TYPE Docs Pull Request COMPONENT NAME ec2_instance ADDITIONAL INFORMATION n/a, only see one bad example here Reviewed-by: Alina Buzachis <None> (cherry picked from commit 4e9aec7)
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #654 🤖 @patchback |
Update ec2_instance.py SUMMARY vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error-> TASK [manage_ec2_instances : Create EC2 instances for ansible node (control node)] ********************************************************************************************************** fatal: [localhost]: FAILED! => changed=false msg: No default subnet could be found - you must include a VPC subnet ID (vpc_subnet_id parameter) to create an instance changing to match other examples ISSUE TYPE Docs Pull Request COMPONENT NAME ec2_instance ADDITIONAL INFORMATION n/a, only see one bad example here Reviewed-by: Alina Buzachis <None> (cherry picked from commit 4e9aec7)
[PR #652/4e9aec79 backport][stable-3] Update ec2_instance.py This is a backport of PR #652 as merged into main (4e9aec7). SUMMARY vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error-> TASK [manage_ec2_instances : Create EC2 instances for ansible node (control node)] ********************************************************************************************************** fatal: [localhost]: FAILED! => changed=false msg: No default subnet could be found - you must include a VPC subnet ID (vpc_subnet_id parameter) to create an instance changing to match other examples ISSUE TYPE Docs Pull Request COMPONENT NAME ec2_instance ADDITIONAL INFORMATION n/a, only see one bad example here
[PR #652/4e9aec79 backport][stable-2] Update ec2_instance.py This is a backport of PR #652 as merged into main (4e9aec7). SUMMARY vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error-> TASK [manage_ec2_instances : Create EC2 instances for ansible node (control node)] ********************************************************************************************************** fatal: [localhost]: FAILED! => changed=false msg: No default subnet could be found - you must include a VPC subnet ID (vpc_subnet_id parameter) to create an instance changing to match other examples ISSUE TYPE Docs Pull Request COMPONENT NAME ec2_instance ADDITIONAL INFORMATION n/a, only see one bad example here
…_ec2_vpc_nat_gateway Migrate ec2_vpc_nat_gateway* modules and tests Depends-On: ansible-collections#410 Remove ec2_vpc_nat_gateway* modules and tests These modules have been migrated to amazon.aws Update runtime.yml with redirects to that collection Update ignore files Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
…_ec2_vpc_nat_gateway Migrate ec2_vpc_nat_gateway* modules and tests Depends-On: ansible-collections#410 Remove ec2_vpc_nat_gateway* modules and tests These modules have been migrated to amazon.aws Update runtime.yml with redirects to that collection Update ignore files Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
SUMMARY
vpc_subnet_id is not configurable under the network key, just tried a copy of the example and got this error->
changing to match other examples
ISSUE TYPE
COMPONENT NAME
ec2_instance
ADDITIONAL INFORMATION
n/a, only see one bad example here