Lost FIP connectivity when schema restarting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
High
|
Sachin Bansal | ||
R1.1 |
Fix Committed
|
High
|
Sachin Bansal | ||
R2.0 |
Fix Committed
|
High
|
Sachin Bansal | ||
R2.1 |
Fix Committed
|
High
|
Sachin Bansal | ||
OpenContrail |
Fix Committed
|
High
|
Édouard Thuleau |
Bug Description
On release 1.10, we lost connectivity with FIP when we restart the schema transformer daemon when it walk the IF-MAP graph.
Our control nodes are peering with MX routers and we defined specific route targets (64516:1, 223.255.254.0:1, 223.255.254.0:255) on the floating IP pool virtual networks (called 'public').
From the control node trace, we saw the route targets on the virtual network are updated:
2015-02-05 10:30:46.500 RoutingInstance
2015-02-05 10:30:46.543 RoutingInstance
2015-02-05 10:30:46.588 RoutingInstance
2015-02-05 10:30:46.631 RoutingInstance
2015-02-05 10:31:26.330 RoutingInstance
2015-02-05 10:31:26.392 RoutingInstance
That the cause the FIP connectivity goes down and not the east-west traffic.
description: | updated |
Changed in juniperopenstack: | |
assignee: | nobody → Sachin Bansal (sbansal) |
Changed in opencontrail: | |
assignee: | nobody → Sachin Bansal (sbansal) |
Changed in juniperopenstack: | |
assignee: | Sachin Bansal (sbansal) → Édouard Thuleau (ethuleau) |
Changed in opencontrail: | |
assignee: | Sachin Bansal (sbansal) → Édouard Thuleau (ethuleau) |
Changed in juniperopenstack: | |
importance: | Undecided → High |
Changed in opencontrail: | |
importance: | Undecided → High |
Changed in juniperopenstack: | |
assignee: | Édouard Thuleau (ethuleau) → Sachin Bansal (sbansal) |
https:/ /review. opencontrail. org/#/c/ 7152/