Bug 1663423 - Router cannot sync routes until recreate it
Summary: Router cannot sync routes until recreate it
Keywords:
Status: CLOSED DUPLICATE of bug 1660598
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Ram Ranganathan
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 09:19 UTC by wangzhida
Modified: 2022-08-04 22:20 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-22 14:45:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description wangzhida 2019-01-04 09:19:57 UTC
Description of problem:

The customer has the env of OCP3.11 with 3master + 30infra + 150+ nodes (holding 1900+ pods)
They running router pods with replica=30 across the infra nodes.

This issue is : when they create a route, some of the routers cannot sync it to their haproxy.conf. and after delete the router pod, the recreated one will be normal.

From the issued router pod, the log will keep reporting below errors:
E1228 11:57:38.516286       1 router_controller.go:250] another route has claimed this host


Concern from the customer:

1. They need detailed info about how router sync routes from api and they doubt the RCA is router doesn't treat api as the default input.For example, api "do" update new route to routers but router refuses to update it.

2. Does it make sense to just using replica=30 to run HA routers in the cluster ?


For sosreport, because of the limit of bugzilla , please download it from case 02282929 #5 with password:redhat


Thank you.

Comment 1 wangzhida 2019-01-09 01:39:53 UTC
any update ?

Comment 8 Ben Bennett 2019-01-14 14:58:07 UTC
@weibin: Can you try to reproduce this please?

Comment 35 Stephen Cuppett 2019-01-22 14:45:25 UTC

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


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