Bug 1789121

Summary:	Router doesn't listen on ipv6 interfaces when cluster network config indicates ipv6 support
Product:	OpenShift Container Platform	Reporter:	Dan Mace <dmace>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, rbryant
Version:	4.3.0
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ipv6
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1789124 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:23:24 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:	1789124

Description Dan Mace 2020-01-08 19:37:48 UTC

Description of problem:

When running on an IPv6-enabled cluster (defined as the presence of an ipv6 address in the network.config.openshift.io `.status.clusterNetwork` list), the router isn't listening on an ipv6 address.

This has already been fixed in https://github.com/openshift/cluster-ingress-operator/pull/342 but we'd like to backport the fix and document the change with a bug report.

Version-Release number of selected component (if applicable):


How reproducible:

Launch a single-stack IPv6 enabled cluster on AWS without the fix.

Actual results:


The router process won't listen on any ipv6 interface.

Expected results:

The router should listen on all available ipv4 and ipv6 interfaces.

Additional info:

Comment 2 Russell Bryant 2020-01-28 21:25:19 UTC

I have tested this successfully

Comment 4 errata-xmlrpc 2020-05-04 11:23:24 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, 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:0581