Bug 1464318

Summary:	[ded-stage-aws]Routes that are created with a path / are now only responding to traffic in / and not any subsequent paths
Product:	OpenShift Online	Reporter:	zhaozhanqi <zzhao>
Component:	Routing	Assignee:	Dan Yocum <dyocum>
Status:	CLOSED CURRENTRELEASE	QA Contact:	zhaozhanqi <zzhao>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, bbennett, bingli, eparis, yadu
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-04 15:59:51 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 zhaozhanqi 2017-06-23 05:28:36 UTC

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:

Comment 1 Ben Bennett 2017-06-23 15:55:30 UTC


*** This bug has been marked as a duplicate of bug 1446360 ***

Comment 2 zhaozhanqi 2017-06-26 02:08:19 UTC

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 13:18:33 UTC

ded-stage-aws needs to be upgraded to 3.5.5.15 (https://access.redhat.com/errata/RHBA-2017:1235)

Comment 4 Dan Yocum 2017-06-26 17:26:31 UTC

(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?

Comment 5 Dan Yocum 2017-06-27 14:15:16 UTC

Is 3.5.5.26 acceptable?

Comment 6 Eric Paris 2017-06-27 23:52:18 UTC

He meant 'anything newer than .15' is acceptable. .26 sounds great.

Comment 7 Dan Yocum 2017-06-30 15:56:32 UTC

Logging is not being deployed correctly.  For this testing do you NEED logging?

Comment 8 Dan Yocum 2017-07-03 17:12:17 UTC

blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1442321

Comment 9 Dan Yocum 2017-07-03 17:20:49 UTC

I've turned the cluster over to QE for testing this bug only.

Comment 10 Yan Du 2017-07-04 06:02:37 UTC

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