Bug 1939740

Summary:	dual stack nodes with OVN single ipv6 fails on bootstrap phase
Product:	OpenShift Container Platform	Reporter:	Daniel Del Ciancio <ddelcian>
Component:	Networking	Assignee:	Dan Winship <danw>
Networking sub component:	runtime-cfg	QA Contact:	Victor Voronkov <vvoronko>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aconstan, anusaxen, asegurap, augol, bdeschen, danw, ddelcian, ohochman, rbrattai, szobair, trwest, zzhao
Version:	4.6	Flags:	asegurap: needinfo-
Target Milestone:	---
Target Release:	4.8.0
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:
Clones:	1942488 (view as bug list)		Environment:
Last Closed:	2021-07-27 22:53:48 UTC	Type:	Bug
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:
Bug Blocks:	1942488

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