Bug 1381584

Summary: Router Sharding Results in Inconsistent or Delayed Results
Product: OpenShift Container Platform Reporter: Steven Walter <stwalter>
Component: NetworkingAssignee: Ram Ranganathan <ramr>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: unspecified CC: aos-bugs, bbennett, erich, stwalter
Version: 3.2.0Keywords: Performance
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-01-27 16:24:18 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:

Description Steven Walter 2016-10-04 13:30:37 UTC 
Description of problem:

Problem 1 :  Routing entries not appearing in haproxy.conf router 
Problem 2 : Route definition created but backend server entries missing.
Problem 3 :  We could see full routing entry successfully created in haproxy.conf file including server entry but URl is not working. After waiting 1 hour, url is working. not sure why? was haproxy not restarting to reflect the changes??
Problem 4 : We tried to toggle router from one project to another project. like project1 has dev router, we tried to toggle it with stage router and assuming all routing entries from dev to move to stage router. It is happening few times, not always. There is no consistency and you can see all 3 problems mentioned here also.

Details in PC.


Version-Release number of selected component (if applicable):
3.2.0, working to get the precise version


How reproducible:
Not yet reproduced

Additional Information:
Using ipfailover, although this shouldn't affect routes
Comment 30 Ben Bennett 2017-01-27 16:24:18 UTC 
I believe this is fixed by https://github.com/openshift/origin/pull/12199

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