BGPaaS: don't create peering relationship between bgpaas-server and MX
Bug #1538320 reported by
amit surana
This bug report is a duplicate of:
Bug #1538318: BGPaaS: don't create peering relationship between bgpaas-server and MX.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Medium
|
Sachin Bansal | ||
Bug Description
A sequence of operations can lead to a spurious relationship between MX bgp-router and bgpaas-server bgp-router object. Once this happens, DM will pick this up and try to configure the bgpaas-server as a MX neighbor, which is not what we want. Configuration commits on MX will fail and impact rest of the system.
the sequence that leads to this:
1. create bgpaas object, attach to vmi.
2. delete bgpaas object.
3. bgp-client object is deleted after step 2, but bgpaas-server object isn't (cause VN/RI are still present)
4. restart config services.
post restart, the bug is seen.
To post a comment you must log in.
