Bug 1942506
| Summary: | [4.6] dual stack nodes with OVN single ipv6 fails on bootstrap phase | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Winship <danw> | ||||||||
| Component: | Networking | Assignee: | Dan Winship <danw> | ||||||||
| Networking sub component: | runtime-cfg | QA Contact: | Daniel Del Ciancio <ddelcian> | ||||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||||
| Severity: | high | ||||||||||
| Priority: | high | CC: | aconstan, asegurap, bdeschen, bnemec, danw, ddelcian, raj.sarvaiya, szobair, talessio, vvoronko, zzhao | ||||||||
| Version: | 4.6 | Keywords: | Triaged | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 4.6.z | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: |
Cause: When bringing up a single-stack IPv6 cluster on nodes with IPv4 addresses, kubelet might use the IPv4 IP as the node IP rather than the IPv6 IP
Consequence: host-network pods have IPv4 IPs rather than IPv6, making them unreachable from IPv6-only pods
Fix: the node-IP-picking code was fixed to handle this case
Result: nodes will have IPv6 IPs, not IPv4
|
Story Points: | --- | ||||||||
| Clone Of: | 1942488 | Environment: | |||||||||
| Last Closed: | 2021-08-12 01:36:41 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: | 1942488 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
|
Comment 2
Dan Winship
2021-05-21 20:03:29 UTC
@raj.sarvaiya I know you have been trying to install a cluster on a newer release (4.7+), but can you verify this bug on 4.6 ? Customer responded that they will test this early next week since there’s no free dev envs at the moment. Once they have results from their testing, they will reply to the BZ directly. Installation completed successfully. Attaching .openshift_install.log and generating must-gather Created attachment 1795508 [details]
openshift-install-log
openshift-install.log
By the way multus issue that was seen previously is still there
> oc describe po envoyv4v6-67f58fc786-sfn9j | grep -i macvlan
> ...
> Warning FailedCreatePodSandBox 32s (x108 over 28m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_envoyv4v6-67f58fc786-sfn9j_bell-services_16d7fd8c-d88d-43c7-ae82-5cda8e1cc940_0(fd82738b09362927f2fbbb5dc4e25c3b38bf9fd5a6a7d651c6ca57641aa52e6e): [bell-services/envoyv4v6-67f58fc786-sfn9j:envoyv4]: error adding container to network "envoyv4": failed to create macvlan: device or resource busy
Created attachment 1795509 [details]
must-gather part 1
must-gather part 1 (aa)
Created attachment 1795510 [details]
must-gather part 2
must-gather part 2 (ab)
Hi @raj.sarvaiya - Can you verify that the cluster still installs fine minus the multus issue ? Our QE team needs to verify the original install bug. Let us know if this can be considered "verified" so we can issue the errata. Hi @raj.sarvaiya - Can you verify that the cluster still installs fine minus the multus issue ? Our QE team needs to verify the original install bug. Let us know if this can be considered "verified" so we can issue the errata. Excluding the multus issue, the cluster does install fine 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.42 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:3008 |