Description of problem: Whereabouts doesn't exclude IPv6 ranges, see: https://github.com/dougbtv/whereabouts/issues/71 How reproducible: Always Steps to Reproduce: Use a range like: ``` "ipam": { "type": "whereabouts", "range": "caa5::0/112", "exclude": ["caa5::0/113"] } ``` Actual results: IP addresses are `caa5::1, caa5::2, etc...` Expected results: First address should be `caa5::8000` Additional info: Upstream PR @ https://github.com/dougbtv/whereabouts/pull/74 master PR @ https://github.com/openshift/whereabouts-cni/pull/36
This has been modified and merged into master @ https://github.com/openshift/whereabouts-cni/pull/36, thanks Weibin for taking a look.
Test results show the first address is caa5::8001, not caa5::8000 [weliang@weliang tools]$ oc exec whereabouts-podv6-5 -- ip a | grep caa5 inet6 caa5::8005/112 scope global [weliang@weliang tools]$ oc exec whereabouts-podv6-4 -- ip a | grep caa5 inet6 caa5::8003/112 scope global [weliang@weliang tools]$ oc exec whereabouts-podv6-3 -- ip a | grep caa5 inet6 caa5::8004/112 scope global [weliang@weliang tools]$ oc exec whereabouts-podv6-2 -- ip a | grep caa5 inet6 caa5::8001/112 scope global [weliang@weliang tools]$ oc exec whereabouts-podv6-1 -- ip a | grep caa5 inet6 caa5::8002/112 scope global [weliang@weliang tools]$ oc get pod NAME READY STATUS RESTARTS AGE whereabouts-podv6-1 1/1 Running 0 2m41s whereabouts-podv6-2 1/1 Running 0 2m40s whereabouts-podv6-3 1/1 Running 0 2m39s whereabouts-podv6-4 1/1 Running 0 2m39s whereabouts-podv6-5 1/1 Running 0 2m38s [weliang@weliang tools]$
Ah ha! Good catch, thanks Weibin :) Turns out Whereabouts was trying to omit the broadcast address, for an IPv6 address, and.... broadcast is not a thing in IPv6! I've got an upstream PR @ https://github.com/dougbtv/whereabouts/pull/77
Tested and verified in 4.7.0-0.nightly-2021-01-05-055003
*** Bug 1898670 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633