-
Notifications
You must be signed in to change notification settings - Fork 350
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
VPC creation "Failed to wait for IPv6 CIDR association" #2363
Labels
Comments
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Nov 6, 2024
…et in vpc (#2374) SUMMARY Fixes: #2363 This PR handles the case in which the vpc does not have ipv6 set and the task to modify it has ipv6_cidr: false ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Bikouo Aubin Reviewed-by: Alina Buzachis Reviewed-by: Helen Bailey <hebailey@redhat.com>
patchback bot
pushed a commit
that referenced
this issue
Jan 8, 2025
…et in vpc (#2374) SUMMARY Fixes: #2363 This PR handles the case in which the vpc does not have ipv6 set and the task to modify it has ipv6_cidr: false ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Bikouo Aubin Reviewed-by: Alina Buzachis Reviewed-by: Helen Bailey <hebailey@redhat.com> (cherry picked from commit f4ff421)
patchback bot
pushed a commit
that referenced
this issue
Jan 8, 2025
…et in vpc (#2374) SUMMARY Fixes: #2363 This PR handles the case in which the vpc does not have ipv6 set and the task to modify it has ipv6_cidr: false ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Bikouo Aubin Reviewed-by: Alina Buzachis Reviewed-by: Helen Bailey <hebailey@redhat.com> (cherry picked from commit f4ff421)
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Jan 8, 2025
…et in vpc (#2374) (#2434) This is a backport of PR #2374 as merged into main (f4ff421). SUMMARY Fixes: #2363 This PR handles the case in which the vpc does not have ipv6 set and the task to modify it has ipv6_cidr: false ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Helen Bailey <hebailey@redhat.com> Reviewed-by: Bikouo Aubin Reviewed-by: GomathiselviS <gomathiselvi@gmail.com>
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Jan 9, 2025
…et in vpc (#2374) (#2433) This is a backport of PR #2374 as merged into main (f4ff421). SUMMARY Fixes: #2363 This PR handles the case in which the vpc does not have ipv6 set and the task to modify it has ipv6_cidr: false ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Helen Bailey <hebailey@redhat.com> Reviewed-by: Mandar Kulkarni <mandar242@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When I try to create a new VPN with
amazon.aws.ec2_vpc_net
(collection v8.2.1) the VPC is created in AWS but the Ansible task fails (after some time) with this message:I can get no other details from Ansible
Issue Type
Bug Report
Component Name
ec2_vpc_net
Ansible Version
Ansible is installed via Homebrew.
Collection Versions
AWS SDK versions
Configuration
OS / Environment
MacBook Pro
Chip: Apple M1 Pro
macOS: Sonoma 14.6.1
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin23)
Homebrew 4.4.2
Steps to Reproduce
Tested with this simple playbook.
Expected Results
Since VPC is correctly created in AWS, I expected the task to succeed in Ansible as well.
Actual Results
VPC is immediately created in AWS, but the Ansible playbook seems stuck for 5 minutes, then fails like this:
Code of Conduct
The text was updated successfully, but these errors were encountered: