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:
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
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