Red Hat Bugzilla – Bug 1368050
Should also set the connection limits for reencrypt and passthrough termination routes
Last modified: 2016-09-27 05:44:56 EDT
Description of problem: From PR https://github.com/openshift/origin/pull/9810, the connection limits are set for edge route(be_edge_http_*) and insecure route(be_http_*), but the reencrypt(be_secure_*) and passthrough route(be_tcp_*) does not have the configuration. Version-Release number of selected component (if applicable): openshift v3.3.0.22 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git openshift3/ose-haproxy-router v3.3.0.22 185850e07ab4 How reproducible: always Steps to Reproduce: 1. Create route with each type 2. Set the connection limits to the routes via annotation $ oc annotate route route haproxy.router.openshift.io/rate-limit-connections=true $ oc annotate route route haproxy.router.openshift.io/rate-limit-connections.rate-tcp=6 3. Check the haproxy config Actual results: The edge route and unsecure route has the rate-limit-connections applied, but the reencrypt route and passthrough route does not have. Expected results: All the types of route should have the configuration. Additional info:
https://github.com/openshift/origin/pull/10513
Checked on build v3.3.0.24 Issue fixed. The reencrypt and passthrough routes can set the connection limits now.
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-2016:1933