Bug 1847969

Summary: IPv6 bare metal deployment with calico has kube-proxy binding on 0.0.0.0 instead of the IPv6 address
Product: OpenShift Container Platform Reporter: Ben Bennett <bbennett>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: openshift-sdn QA Contact: Boris Deschenes <bdeschen>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: anbhat, aojeagar, bbennett, bdeschen, dcbw, dosmith, jtanenba, mcornea, zzhao
Version: 4.4Keywords: Reopened
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1831006 Environment:
Last Closed: 2020-10-12 15:47:56 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: 1831006    
Bug Blocks: 1833048    

Comment 2 Antonio Ojea 2020-06-17 13:40:49 UTC

*** This bug has been marked as a duplicate of bug 1833048 ***

Comment 16 zhaozhanqi 2020-09-24 02:13:13 UTC
Hi, Boris
could you help verified this bug with calico on 4.5 version with ipv6 cluster?

Comment 19 Boris Deschenes 2020-09-28 13:24:22 UTC
this has been fixed and a single-stack IPv6 deployment now sees its kube-proxy binds to :: instead of 0.0.0.0 during calico deployment.. thank you

Comment 20 Boris Deschenes 2020-09-28 13:24:50 UTC
this has been fixed and a single-stack IPv6 deployment now sees its kube-proxy binds to :: instead of 0.0.0.0 during calico deployment.. thank you

Comment 21 Jacob Tanenbaum 2020-10-06 18:53:20 UTC
this bug was mistakenly closed instead of set to verified

Comment 23 errata-xmlrpc 2020-10-12 15:47:56 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 (OpenShift Container Platform 4.5.14 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-2020:3843