Verified with a cluster (4.6.0-0.ci.test-2020-11-17-064446-ci-ln-01jzfzt) launched by cluster-bot and passed. # oc annotate route edgeroute haproxy.router.openshift.io/timeout=100d route.route.openshift.io/edgeroute annotated # oc get route edgeroute -oyaml apiVersion: route.openshift.io/v1 kind: Route metadata: annotations: haproxy.router.openshift.io/timeout: 100d # oc -n openshift-ingress exec router-default-c9ccc9f7-5m9pn -- cat haproxy.config <---snip---> # Plain http backend or backend with TLS terminated at the edge or a # secure backend with re-encryption. backend be_edge_http:hongli1:edgeroute mode http option redispatch option forwardfor balance leastconn timeout server 2147483647ms sh-4.4$ rpm -qa | grep haproxy haproxy20-2.0.16-3.el8.x86_64
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.6.6 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:5115