Bug 1347824

Summary: dev-preview-stg not properly routing
Product: OpenShift Online Reporter: Erik M Jacobs <ejacobs>
Component: RoutingAssignee: Ben Bennett <bbennett>
Status: CLOSED CURRENTRELEASE QA Contact: zhaozhanqi <zzhao>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.xCC: aos-bugs, dakini
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-17 18:41:54 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:

Description Erik M Jacobs 2016-06-17 18:17:37 UTC 
Description of problem:
http://tasks-route-demo2.b795.dev-preview-stg.openshiftapps.com/ is not being properly routed.

* route points to service:
NAME          HOST/PORT                                                  PATH      SERVICE                  TERMINATION   LABELS
tasks-route   tasks-route-demo2.b795.dev-preview-stg.openshiftapps.com             tasks-service:8080-tcp                 app=tasks

* service has endpoint
oc get ep tasks-service
NAME            ENDPOINTS                                      AGE
tasks-service   10.1.8.18:8443,10.1.8.18:8778,10.1.8.18:8080   17m


* router is giving me a 503:
[thoraxe:~/Red_Hat/workspace/jboss-tasks-rs] template-and-tweaks* ± curl -vvv http://tasks-route-demo2.b795.dev-preview-stg.openshiftapps.com/
*   Trying 52.73.177.49...
* Connected to tasks-route-demo2.b795.dev-preview-stg.openshiftapps.com (52.73.177.49) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.40.0
> Host: tasks-route-demo2.b795.dev-preview-stg.openshiftapps.com
> Accept: */*
> 
* HTTP 1.0, assume close after body
< HTTP/1.0 503 Service Unavailable
< Pragma: no-cache
< Cache-Control: private, max-age=0, no-cache, no-store
< Connection: close
< Content-Type: text/html
Comment 1 Stefanie Forrester 2016-06-17 18:41:14 UTC 
The router pod has been updated and now appears to be routing properly. (The old image contained a bug that has now been fixed.)