-
Notifications
You must be signed in to change notification settings - Fork 349
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
Improve doc to show support for IPv6 CIDR block #634
Improve doc to show support for IPv6 CIDR block #634
Conversation
Build failed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to try and improve the docs and tests.
It looks like some random pasting errors crept in.
Build failed.
|
recheck |
Build failed.
|
@alinabuzachis , FYI this PR will fail integration tests until #631 is merged. |
- cidr: 10.228.231.0/24 | ||
assign_instances_ipv6: true | ||
# Carve first /64 subnet of the Amazon-provided CIDR for the VPC. | ||
ipv6_cidr: "{{ vpc_ipv6_cidr_block | ansible.netcommon.ipsubnet(64, 1) }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initially I was testing with a /120 prefix length, not a /64.
However, that caused the test to be stuck, and I uncovered ansible-collections/ansible.utils#132 and netaddr/netaddr#241
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sebastien-rosset Thank you. LGTM!
@sebastien-rosset this PR contains the following merge commits: Please rebase your branch to remove these commits. |
…s for IPv6 route table
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
25c4e19
to
eddce97
Compare
recheck |
regate |
1 similar comment
regate |
It seems it stucks gating this PR.
regate |
regate |
regate |
Backport to stable-2: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply c06d77c on top of patchback/backports/stable-2/c06d77c94a70a767566464b299410a27ea55f3e1/pr-634 Backporting merged PR #634 into main
🤖 @patchback |
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #751 🤖 @patchback |
Improve doc to show support for IPv6 CIDR block SUMMARY Improve doc to show IPv6 CIDR blocks are supported. Add example with IPv6 CIDR block. Add missing attribute to return values. Remove duplicate assertions in integration tests. Add tests for IPv6 subnets in integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_route_table ADDITIONAL INFORMATION While testing IPv6 in this module, I discovered the ipsubnet filter does not work if the prefix length has a fairly high value such as /120. I was running an integration test with a /120 subnet in this PR, but the ipsubnet call never returns and uses 100% CPU. I changed the value to a /64 subnet so this PR can pass. The ipsubnet issue needs to be fixed in ansible.netcommon and the netaddr package. I've created a unit test to reproduce the problem: ansible-collections/ansible.netcommon#362 The integration tests in this PR depend on #631 for the VPC configuration. Reviewed-by: Mark Chappell <None> Reviewed-by: Sebastien Rosset <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Jill R <None> (cherry picked from commit c06d77c)
[PR #634/c06d77c9 backport][stable-3] Improve doc to show support for IPv6 CIDR block This is a backport of PR #634 as merged into main (c06d77c). SUMMARY Improve doc to show IPv6 CIDR blocks are supported. Add example with IPv6 CIDR block. Add missing attribute to return values. Remove duplicate assertions in integration tests. Add tests for IPv6 subnets in integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_route_table ADDITIONAL INFORMATION While testing IPv6 in this module, I discovered the ipsubnet filter does not work if the prefix length has a fairly high value such as /120. I was running an integration test with a /120 subnet in this PR, but the ipsubnet call never returns and uses 100% CPU. I changed the value to a /64 subnet so this PR can pass. The ipsubnet issue needs to be fixed in ansible.netcommon and the netaddr package. I've created a unit test to reproduce the problem: ansible-collections/ansible.netcommon#362 The integration tests in this PR depend on #631 for the VPC configuration.
) (ansible-collections#751) [PR ansible-collections#634/c06d77c9 backport][stable-3] Improve doc to show support for IPv6 CIDR block This is a backport of PR ansible-collections#634 as merged into main (c06d77c). SUMMARY Improve doc to show IPv6 CIDR blocks are supported. Add example with IPv6 CIDR block. Add missing attribute to return values. Remove duplicate assertions in integration tests. Add tests for IPv6 subnets in integration tests. ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_route_table ADDITIONAL INFORMATION While testing IPv6 in this module, I discovered the ipsubnet filter does not work if the prefix length has a fairly high value such as /120. I was running an integration test with a /120 subnet in this PR, but the ipsubnet call never returns and uses 100% CPU. I changed the value to a /64 subnet so this PR can pass. The ipsubnet issue needs to be fixed in ansible.netcommon and the netaddr package. I've created a unit test to reproduce the problem: ansible-collections/ansible.netcommon#362 The integration tests in this PR depend on ansible-collections#631 for the VPC configuration.
…new-tiny_prefix-variable_5260 tests: use the new tiny_prefix variable SUMMARY The new tiny_prefix variable has recently been introduced. It's a 12 characters long string that is reused for the whole job. ISSUE TYPE Bugfix Pull Request COMPONENT NAME tests Reviewed-by: Dmytro Vorotyntsev <None> Reviewed-by: Mark Chappell <None> Reviewed-by: None <None>
SUMMARY
ISSUE TYPE
COMPONENT NAME
ec2_vpc_route_table
ADDITIONAL INFORMATION
ipsubnet
filter does not work if the prefix length has a fairly high value such as/120
.ipsubnet
call never returns and uses 100% CPU. I changed the value to a /64 subnet so this PR can pass.ipsubnet
issue needs to be fixed in ansible.netcommon and the netaddr package. I've created a unit test to reproduce the problem: Add unit tests for ipsubnet filter and IPv6 ansible.netcommon#362