Configured route-target missing from routing-instance object
Bug #1329522 reported by
Sunil Bakhru
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
Incomplete
|
High
|
Ashish Ranjan | ||
Bug Description
In a 5 node setup with 3 controller/2 compute, BGP routes of some VM specific routing-instances were not getting exported to MX. MX has routing-instances configured with particular route-targets and VNs are created in Contrail with the same route-target. Through introspect, we could confirm that the VN object includes the configured route-target, but the RI object does not show the same.
Contrail-schema restart fixes the problem.
| Changed in opencontrail: | |
| importance: | Undecided → High |
| assignee: | nobody → Ashish Ranjan (aranjan-n) |
| description: | updated |
Revision history for this message
| Nagabhushana R (bhushana) wrote | #1 |
| affects: | opencontrail → juniperopenstack |
| Changed in juniperopenstack: | |
| status: | New → Incomplete |
| tags: | added: config |
To post a comment you must log in.
Sunil,
Release/Branch and build information is missing. Can you please update if you still see the issue in a specific scenario...?
Also, I moved the bug from opencontrail project to juniperopenstack. All internal bug reporting must be on juniperopenstack project.