Bug 1374772

Summary: Editing routes doesn't properly clean up the config
Product: OpenShift Container Platform Reporter: Ben Bennett <bbennett>
Component: NetworkingAssignee: Rajat Chopra <rchopra>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, bmeng, hongli, pruan, trankin, vlaad, zhaliu
Version: 3.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Services weren't being updated correctly on an edit. Consequence: When you edited a service, both the old and new values for the services would remain, so requests would still go to the old service. Fix: Change the code to handle the update correctly. Result: The routes only send traffic to the new service.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-04 12:43:50 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 Ben Bennett 2016-09-09 15:05:38 UTC 
Description of problem:
If you edit a route and change the service from A to B, rather than 100% of the traffic going to B, the traffic is instead split between A and B.

Version-Release number of selected component (if applicable):
kubernetes v1.2.0-36-g4a3f9c5

How reproducible:
Always

Steps to Reproduce:
1. Create app A and B: oc new-app https://github.com/spinolacastro/teste#a --name app-a oc new-app https://github.com/spinolacastro/teste#b --name app-b
2. Expose the route to service A: oc expose svc/app-a --name abtest At this point, the traffic is correctly forwarded to service A.
3. Edit the route to expose service B: oc patch routes/abtest -p '{"spec":{"to":{"name": "app-b"}}}'


Actual results:
Traffic is split between pods for service A and B.

Expected results:
Traffic goes exclusively to pods for service B.


Additional info:
Comment 1 Ben Bennett 2016-09-09 15:11:49 UTC 
This is fixed in 3.0 origin by https://github.com/openshift/origin/pull/10855

It needs to go in 3.1 OSE
Comment 2 Ben Bennett 2016-09-14 14:04:44 UTC 
*** Bug 1375861 has been marked as a duplicate of this bug. ***
Comment 3 Ben Bennett 2016-09-29 20:01:12 UTC 
Ignore my versions abocve.  I meant 1.3.0 origin, and 3.3.1 OSE
Comment 7 errata-xmlrpc 2016-10-04 12:43:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1988
Comment 8 zhaliu 2016-10-14 10:13:45 UTC 
I have verified this issue on STG 3.3.0.35,and no problems are found.

kubernetes v1.3.0+52492b4
openshift v3.3.0.35