Bug 1503637
| Summary: | Setting 'timeout server' twice per backend | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Paris <eparis> |
| Component: | Networking | Assignee: | Ivan Chavero <ichavero> |
| Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | aos-bugs, bbennett, bmeng, eparis, yadu |
| Version: | 3.7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No doc update
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-05 09:29:37 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: | |||
The directive will appear if ROUTER_DEFAULT_SERVER_TIMEOUT is set and if there's this annotation on reouter definition: haproxy.router.openshift.io/timeout Is this being specifically setup or is happening when there are default values? Verified this bug on v3.7.0-0.190.0 Set the timeout for the route $oc annotate route service-unsecure haproxy.router.openshift.io/timeout=3s Check the haproxy.config: backend be_http:zq:service-unsecure mode http option redispatch option forwardfor balance roundrobin timeout server 3s timeout check 5000ms 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-2018:0636 |
registry.ops.openshift.com/openshift3/ose-haproxy-router:v3.7.0-0.143.3 I see: [WARNING] 290/134805 (70512) : parsing [/var/lib/haproxy/conf/haproxy.config:65696] : overwriting 'timeout server' which was already specified Then looking in haproxy.config I see: # Plain http backend backend be_http:eparis:mysql mode http option redispatch option forwardfor balance leastconn timeout server 6000s timeout server 6000s timeout check 5000ms http-request set-header X-Forwarded-Host %[req.hdr(host)] http-request set-header X-Forwarded-Port %[dst_port] http-request set-header X-Forwarded-Proto http if !{ ssl_fc } http-request set-header X-Forwarded-Proto https if { ssl_fc } http-request set-header Forwarded for=%[src];host=%[req.hdr(host)];proto=%[req.hdr(X-Forwarded-Proto)] cookie 375f768162a6325b8c5955d0ac580c09 insert indirect nocache httponly server pod:mysql-1-pcgdb:mysql:10.130.22.80:3306 10.130.22.80:3306 cookie d7a223c82911fcca53f8e25f62d412a6 weight 200 check inter 5000ms