Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2053353

Summary:	Using ipv6 egressip does not work on baremetal when the destination is ipv6
Product:	OpenShift Container Platform	Reporter:	Swapnil Dalela <sdalela>
Component:	Networking	Assignee:	Patryk Diak <pdiak>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	achernet, anbhat, huirwang, surya
Version:	4.8
Target Milestone:	---
Target Release:	4.11.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-21 14:18:31 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:

Description Swapnil Dalela 2022-02-11 03:53:39 UTC

Description of problem:

When using multiple egressip objects, for eg: one ipv4 and ipv6, only ipv4 egress ip is used but not ipv6 one. When the destination is ipv6, ip of node running the pod is used. When the destination is ipv4, the egressip works as intended.


How reproducible:

Always


Steps to Reproduce:
1. Have a pod match a selector for an EgressIP object with two egress IP addresses(ipv4 and ipv6).
2. Access a destination outside cluster with ipv4(works as intended).
3. Access the same destination outside cluster with ipv6.

Actual results:

ipv6 egressip is not used when destination is ipv6.


Expected results: 

ipv6 egressip should be used.