Bug 1479392

Summary: Traffic splitting is based on # of pods and not on % per service
Product: OpenShift Container Platform Reporter: Dan McPherson <dmcphers>
Component: NetworkingAssignee: Phil Cameron <pcameron>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, pcameron
Version: 3.6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:41:15 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 Dan McPherson 2017-08-08 13:31:05 UTC 
Description of problem:

If I have two services and a route splitting traffic 50/50 between them, the actual split is based on how many pods there are for each service.  So if service A has 4 pods and service B has 1 pods, service A will get 4 times the traffic that service B does.



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


How reproducible:
100%


Steps to Reproduce:
1. Create two services (with different home pages so you can tell the difference (Ex: 1 ruby and 1 python)).  One with 4 pods and one with 1 pod.
2. Create a route that splits traffic 50/50 between them.
3. Hit the route 10 times (from new incognito windows for each hit) and you will see that you got 8 results from 1 service and 2 from the other.

Actual results:

8 hits from 1 service and 2 from the other


Expected results:

5 hits from each service


Additional info:

This may be expected behavior from the routing tier, although I would argue it's not the desired behavior, but at a minimum this is not the expected behavior given the text in the UI/docs.
Comment 1 Dan McPherson 2017-08-08 14:12:08 UTC 
Note I did this with oc cluster up.  openshift.com seems to have a little more random results.
Comment 2 Phil Cameron 2017-08-08 14:41:15 UTC 
This is fixed in 1470350
PR 15309

*** This bug has been marked as a duplicate of bug 1470350 ***
Comment 3 Phil Cameron 2017-08-08 14:43:30 UTC 
Also openshift-docs PR 4847