Red Hat Bugzilla – Bug 1464318
[ded-stage-aws]Routes that are created with a path / are now only responding to traffic in / and not any subsequent paths
Last modified: 2017-07-04 11:59:51 EDT
Description of problem:
Create route with a path "/", the route cannot access the sub path
example.com --> OK
example.com/test --> NOT OK
Version-Release number of selected component (if applicable):
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
step 3 return 503
step 3 should be accessed.
*** 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 184.108.40.206 (https://access.redhat.com/errata/RHBA-2017:1235)
(In reply to Ben Bennett from comment #3)
> ded-stage-aws needs to be upgraded to 220.127.116.11
The latest GA release is 18.104.22.168. Any objections to having that put on ded-stage-aws?
Is 22.214.171.124 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.
# 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/