Description of problem: Create route with a path "/", the route cannot access the sub path ie. Route: example.com Path: / example.com --> OK example.com/test --> NOT OK Version-Release number of selected component (if applicable): ded-stage-aws 3.5.5.10 How reproducible: always Steps to Reproduce: 1. Create pod/service oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/caddy-docker.json oc create -f oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/edge/service_unsecure.json 2. Create route with path '/' oc expose svc service-unsecure --path=/ 3. access the route curl $route/test/ Actual results: step 3 return 503 Expected results: step 3 should be accessed. Additional info:
*** This bug has been marked as a duplicate of bug 1446360 ***
hi Ben Bennett yes, this bug happened in 3.5 before and also it had been fixed. but this bug still happened on **ded-stage-aws** env. please help check.
ded-stage-aws needs to be upgraded to 3.5.5.15 (https://access.redhat.com/errata/RHBA-2017:1235)
(In reply to Ben Bennett from comment #3) > ded-stage-aws needs to be upgraded to 3.5.5.15 > (https://access.redhat.com/errata/RHBA-2017:1235) The latest GA release is 3.5.5.26. Any objections to having that put on ded-stage-aws?
Is 3.5.5.26 acceptable?
He meant 'anything newer than .15' is acceptable. .26 sounds great.
Logging is not being deployed correctly. For this testing do you NEED logging?
blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1442321
I've turned the cluster over to QE for testing this bug only.
Test on ded-stage-aws, the bug have been fixed. openshift v3.5.5.26 kubernetes v1.5.2+43a9be4 # oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD service-unsecure service-unsecure-d2.5c20.ded-stage-aws.openshiftapps.com / service-unsecure http None # curl http://service-unsecure-d2.5c20.ded-stage-aws.openshiftapps.com/test/ Hello-OpenShift-Path-Test http-8080