Bug 1847969 - IPv6 bare metal deployment with calico has kube-proxy binding on 0.0.0.0 instead of the IPv6 address
Summary: IPv6 bare metal deployment with calico has kube-proxy binding on 0.0.0.0 inst...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.z
Assignee: Ben Bennett
QA Contact: Boris Deschenes
URL:
Whiteboard:
Depends On: 1831006
Blocks: 1833048
TreeView+ depends on / blocked
 
Reported: 2020-06-17 13:07 UTC by Ben Bennett
Modified: 2020-10-12 15:48 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1831006
Environment:
Last Closed: 2020-10-12 15:47:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 624 0 None closed [release-4.4] bug 1833048: For third party plugins enable testing of IPv6 single stack 2020-11-02 06:15:39 UTC
Red Hat Product Errata RHBA-2020:3843 0 None None None 2020-10-12 15:48:20 UTC

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