Bug 1464318 - [ded-stage-aws]Routes that are created with a path / are now only responding to traffic in / and not any subsequent paths
[ded-stage-aws]Routes that are created with a path / are now only responding ...
Product: OpenShift Online
Classification: Red Hat
Component: Routing (Show other bugs)
All All
medium Severity medium
: ---
: ---
Assigned To: Dan Yocum
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2017-06-23 01:28 EDT by zhaozhanqi
Modified: 2017-07-04 11:59 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-04 11:59:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description zhaozhanqi 2017-06-23 01:28:36 EDT
Description of problem:
Create route with a path "/", the route cannot access the sub path 
Route: example.com
Path: /

example.com --> OK
example.com/test --> NOT OK

Version-Release number of selected component (if applicable):

How reproducible:

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:
Comment 1 Ben Bennett 2017-06-23 11:55:30 EDT

*** This bug has been marked as a duplicate of bug 1446360 ***
Comment 2 zhaozhanqi 2017-06-25 22:08:19 EDT
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.
Comment 3 Ben Bennett 2017-06-26 09:18:33 EDT
ded-stage-aws needs to be upgraded to (https://access.redhat.com/errata/RHBA-2017:1235)
Comment 4 Dan Yocum 2017-06-26 13:26:31 EDT
(In reply to Ben Bennett from comment #3)
> ded-stage-aws needs to be upgraded to
> (https://access.redhat.com/errata/RHBA-2017:1235)

The latest GA release is  Any objections to having that put on ded-stage-aws?
Comment 5 Dan Yocum 2017-06-27 10:15:16 EDT
Is acceptable?
Comment 6 Eric Paris 2017-06-27 19:52:18 EDT
He meant 'anything newer than .15' is acceptable. .26 sounds great.
Comment 7 Dan Yocum 2017-06-30 11:56:32 EDT
Logging is not being deployed correctly.  For this testing do you NEED logging?
Comment 8 Dan Yocum 2017-07-03 13:12:17 EDT
blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1442321
Comment 9 Dan Yocum 2017-07-03 13:20:49 EDT
I've turned the cluster over to QE for testing this bug only.
Comment 10 Yan Du 2017-07-04 02:02:37 EDT
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

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