Bug 1931953
| Summary: | Whereabouts IPv6 addresses not calculated when leading hextets equal 0 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Douglas Smith <dosmith> |
| Component: | Networking | Assignee: | Douglas Smith <dosmith> |
| Networking sub component: | multus | QA Contact: | Weibin Liang <weliang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | bbennett, dosmith, jseunghw, weliang |
| Version: | 4.5 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Improper calculation of IPv6 address caused IPv6 addresses that began with leading zeroes to be not be calculated, and those IP addresses would not be assigned.
Consequence: Only IPv6 addresses that did not begin with leading zeroes would be calculated.
Fix: IPv6 calculation method improved.
Result: IPv6 addresses with leading zeroes are calculated properly.
|
Story Points: | --- |
| Clone Of: | 1931950 | Environment: | |
| Last Closed: | 2021-04-27 14:20:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1931950 | ||
| Bug Blocks: | |||
|
Comment 3
Weibin Liang
2021-04-13 15:12:54 UTC
verification still failed in 4.6.0-0.nightly-2021-04-14-130926 Warning FailedCreatePodSandBox 11s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-podv6-1_test_3b8f3958-eff9-47c5-9cb8-bcf7389e4e83_0(9a1bd8eaa6613b528978919622ca4021f9f38f7d2068c0e008b7d910acafe923): [test/whereabouts-podv6-1:whereabouts]: error adding container to network "whereabouts": netplugin failed with no error message [weliang@weliang ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2021-04-14-130926 True False 38m Cluster version is 4.6.0-0.nightly-2021-04-14-130926 [weliang@weliang ~]$ Tested and verified in 4.6.0-0.nightly-2021-04-16-034018
[weliang@weliang Config]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.0-0.nightly-2021-04-16-034018 True False 31m Cluster version is 4.6.0-0.nightly-2021-04-16-034018
[weliang@weliang Config]$ oc exec whereabouts-podv6-1 -- ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: eth0@if114: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8951 qdisc noqueue state UP group default
link/ether 0a:58:0a:81:02:69 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.129.2.105/23 brd 10.129.3.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::80fd:fdff:fea4:e624/64 scope link
valid_lft forever preferred_lft forever
4: net1@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc noqueue state UP group default
link/ether 4a:58:06:d7:28:b5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fd:dead:beef:1::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4858:6ff:fed7:28b5/64 scope link
valid_lft forever preferred_lft forever
[weliang@weliang Config]$
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 (OpenShift Container Platform 4.6.26 bug fix 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/RHBA-2021:1232 |