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

Bug 1789687

Summary:	the env ROUTER_IP_V4_V6_MODE should uses v6 instead v6_only
Product:	OpenShift Container Platform	Reporter:	Hongan Li <hongli>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	high	CC:	aos-bugs
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:23:58 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 Hongan Li 2020-01-10 06:52:02 UTC

Description of problem:
https://github.com/openshift/cluster-ingress-operator/blob/73c67035ea51f1bf577a39020c888de44be7dbd7/pkg/operator/controller/ingress/deployment.go#L428

https://github.com/openshift/router/blob/8af16cfb1e7bb1a0acf89f96c4e18529d591ec4d/images/router/haproxy/conf/haproxy-config.template#L152

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-01-08-181129-ipv6.1

How reproducible:
100%

Steps to Reproduce:
1. install IPv6 cluster on AWS
2.
3.

Actual results:
the clusterNetwork uses IPv6 address but haproxy is still listening on :80/:443 port.

Expected results:
should listing on :::80/:::443 port

Additional info:

Comment 2 Hongan Li 2020-03-24 05:53:05 UTC

verified with 4.4.0-0.nightly-2020-03-23-010639 and the issue has been fixed.

$ oc -n openshift-ingress get deployment -oyaml
<---snip--->
          - name: ROUTER_IP_V4_V6_MODE
            value: v6

$ oc -n openshift-ingress rsh router-default-9f487f848-6896b
sh-4.2$ grep bind haproxy.config 
<---snip--->
  bind :::80 v6only
  bind :::443 v6only

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