| Summary: | Scaled up gear shows as down status in haproxy-status page for cartridge with ssl_to_gear enabled which actually is up | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Meng Bo <bmeng> |
| Component: | Containers | Assignee: | Rob Millner <rmillner> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.x | CC: | mfisher, rmillner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-17 13:32:49 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: | |
Checked with the cartridge mock-0.3, the above problem is gone. But for scaling app, after scale-up, the new gear can be accessed via gear dns, but show as down in the /haproxy-status page. 1. Create mock-0.3 scalable app 2. Scale up the app 3. Check the haproxy-status page # curl -s -3 -k https://mock1s-bmengdev.dev.rhcloud.com/haproxy-status/ |grep 5248ec415fb3270979000009 </tr><tr class="frontend"><td class=ac><a name="express/Frontend"></a><a class=lfsb href="#express/Frontend">Frontend</a></td><td colspan=3></td><td>0</td><td>2</td><td>-</td><td>0</td><td>1</td><td>128</td><td>5</td><td></td><td><span class="rls">6</span>300</td><td><span class="rls">8</span>530</td><td>0</td><td>0</td><td>0</td><td></td><td></td><td></td><td></td><td class=ac>OPEN</td><td class=ac colspan=8></td></tr><tr class="active0"><td class=ac><a name="express/gear-5248ec415fb3270979000009-bmengdev"></a><a class=lfsb href="#express/gear-5248ec415fb3270979000009-bmengdev">gear-5248ec415fb3270979000009-bmengdev</a></td><td>0</td><td>0</td><td>-</td><td>0</td><td>0</td><td></td><td>0</td><td>0</td><td>-</td><td>0</td><td>0</td><td>0</td><td>0</td><td></td><td>0</td><td></td><td>0</td><td title="Connection resets during transfers: 0 client, 0 server"><u>0</u></td><td>0</td><td>0</td><td class=ac>5m52s DOWN</td><td class=ac title="Layer4 connection problem: Connection refused"><u> L4CON in 0ms</u></td><td class=ac>1</td><td class=ac>Y</td><td class=ac>-</td><td title="Failed Health Checks"><u>0</u></td><td>1</td><td>5m52s</td><td class=ac>-</td></tr> 4. Check the gear directly # curl -I -3 -k https://5248ec415fb3270979000009-bmengdev.dev.rhcloud.com/ HTTP/1.1 200 OK Date: Mon, 30 Sep 2013 03:18:55 GMT Server: WEBrick/1.3.1 (Ruby/1.9.3/2013-06-27) OpenSSL/1.0.0 Etag: 17c0097-3d-5248ebba Content-Type: text/html; charset=UTF-8 Content-Length: 61 Last-Modified: Mon, 30 Sep 2013 03:10:50 GMT Vary: Accept-Encoding,User-Agent ProxyTime: D=14086 Pull request: https://github.com/openshift/origin-server/pull/3740 Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/ec9aaaa70076781e0e60c45687b334fbf6fa639c Bug 1013334 - Was exposing the wrong port. Tested on devenv_3863 with mock-0.3 cartridge. The issue fixed, move bug to verified. |
Description of problem: Create cartridge with ssl_to_gear enabled. Create app with the cartridge. Visit the app home page via browser. Will get 502 error. Endpoints: - Private-IP-Name: IP Private-Port-Name: PORT Private-Port: 8080 Public-Port-Name: PROXY_PORT Option: ssl_to_gear: true Mappings: - Frontend: "" Backend: "" Options: websocket: true ssl_to_gear: true - Frontend: "/health" Backend: "" Options: { health: true } For the scalable app, the ENV SSL_TO_GEAR will be added to the gear, and the haproxy.cfg using "mode tcp " and "option ssl-hello-chk", but the gear is in down stauts. Version-Release number of selected component (if applicable): devenv_3844 How reproducible: always Steps to Reproduce: 1. Create app with ssl_to_gear enable cartridge 2. Visit the ssl_to_gear enable frontend 3. Actual results: Will get 502 bad gateway error. Expected results: App should can be accessed. Additional info: Also tried cartridge in this repo, https://github.com/teddythetwig/origin-server/blob/ssl_to_gear/cartridges/openshift-origin-cartridge-mock-ssl/metadata/manifest.yml, get the same error.