Bug 1939740 - dual stack nodes with OVN single ipv6 fails on bootstrap phase
Summary: dual stack nodes with OVN single ipv6 fails on bootstrap phase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: Dan Winship
QA Contact: Victor Voronkov
URL:
Whiteboard:
Depends On:
Blocks: 1942488
TreeView+ depends on / blocked
 
Reported: 2021-03-16 22:28 UTC by Daniel Del Ciancio
Modified: 2023-09-15 01:33 UTC (History)
12 users (show)

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
Clone Of:
: 1942488 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:53:48 UTC
Target Upstream Version:
Embargoed:
asegurap: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift baremetal-runtimecfg pull 130 0 None open Bug 1939740: sort AddressesDefault by ifindex and IPv4/IPv6 preference 2021-03-19 17:23:06 UTC
Github openshift machine-config-operator pull 2478 0 None open Bug 1939740: Use new --prefer-ipv6 flag to "runtimecfg node-ip" as appropriate 2021-03-22 15:12:09 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:54:20 UTC

Comment 1 Dan Winship 2021-03-17 15:50:15 UTC 
So the MCO templates know whether the cluster is single-stack IPv4, single-stack IPv6, or dual-stack (`.IPFamilies` variable in the template) but in the UPI case (https://github.com/openshift/machine-config-operator/blob/master/templates/common/_base/units/nodeip-configuration.service.yaml) we don't pass any args to the node-ip util, so it has no way to know which family we want. So I guess we'll need to pass some argument and then update node-ip (https://github.com/openshift/baremetal-runtimecfg/blob/master/cmd/runtimecfg/node-ip.go) to take that into account.
Comment 3 zhaozhanqi 2021-03-22 07:54:34 UTC 
@vvoronko Could you help verified this bug, thanks.
Comment 5 Dan Winship 2021-03-22 14:38:48 UTC 
sorry, this shouldn't have gone to QA yet; it needs an MCO fix in addition to the runtimecfg fix
Comment 8 Antoni Segura Puimedon 2021-03-24 19:28:55 UTC 
Needinfo was solved by Dan in https://bugzilla.redhat.com/show_bug.cgi?id=1939740#c6
Comment 16 errata-xmlrpc 2021-07-27 22:53:48 UTC 
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.8.2 bug fix and security 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-2021:2438
Comment 17 Red Hat Bugzilla 2023-09-15 01:33:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days
Note You need to log in before you can comment on or make changes to this bug.