Bug 1347824 - dev-preview-stg not properly routing
Summary: dev-preview-stg not properly routing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Routing
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-17 18:17 UTC by Erik M Jacobs
Modified: 2016-06-17 18:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 18:41:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.)


Note You need to log in before you can comment on or make changes to this bug.