Bug 2053353 - Using ipv6 egressip does not work on baremetal when the destination is ipv6
Summary: Using ipv6 egressip does not work on baremetal when the destination is ipv6
Keywords:
Status: CLOSED DUPLICATE of bug 2057931
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 4.11.0
Assignee: Patryk Diak
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-11 03:53 UTC by Swapnil Dalela
Modified: 2022-05-09 10:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-21 14:18:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.