Juniper Openstack

Stabilize bgp_mvpn_test2

Bug #1777488 reported by Ananth Suryanarayana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Fix Committed
Undecided
Ananth Suryanarayana
Juniper Openstack r5.0.1
Trunk
Fix Committed
Undecided
Ananth Suryanarayana
Juniper Openstack r5.1.0

Bug Description

MVPN Neighbor information is not verified correctly, after bgp router id changes. It can so happen that after router-id is changed, before the router-id change is fully processed, part of the verification (over old data) is complete. Later the test fails when verifying against new data, especially the new RouterId information from the neighbor.

Fix by ensuring that MvpnNeighbor info is checked correctly with retry over entire type1 routes lookup

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/43923
Submitter: Ananth Suryanarayana (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R5.0

Review in progress for https://review.opencontrail.org/43924
Submitter: Ananth Suryanarayana (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/43923
Committed: http://github.com/Juniper/contrail-controller/commit/535f4fba1b611fdafe8f6b2dd48aae16904385bf
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 535f4fba1b611fdafe8f6b2dd48aae16904385bf
Author: Ananth Suryanarayana <email address hidden>
Date: Mon Jun 18 10:26:05 2018 -0700

Verify MvpnNeigbor correctly after BGP RouterID change

MVPN Neighbor information is not verified correctly, after bgp router
id changes. It can so happen that after router-id is changed, before
the router-id change is fully processed, part of the verification over
old data is complete. Later the test fails when verifying against new
data, especially the new RouterId information from the neighbor.

Fix by ensuring that MvpnNeighbor info is checked correctly with retry
over entire type1 routes lookup

Change-Id: I836451c7e4f2487f19850fe94cfdcefe1c3b1aca
Closes-Bug: 1777488

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/43924
Committed: http://github.com/Juniper/contrail-controller/commit/ed9f2654d2930367b31da4fff7b2e60986b5fb5b
Submitter: Zuul v3 CI (<email address hidden>)
Branch: R5.0

commit ed9f2654d2930367b31da4fff7b2e60986b5fb5b
Author: Ananth Suryanarayana <email address hidden>
Date: Mon Jun 18 10:26:05 2018 -0700

Verify MvpnNeigbor correctly after BGP RouterID change

MVPN Neighbor information is not verified correctly, after bgp router
id changes. It can so happen that after router-id is changed, before
the router-id change is fully processed, part of the verification over
old data is complete. Later the test fails when verifying against new
data, especially the new RouterId information from the neighbor.

Fix by ensuring that MvpnNeighbor info is checked correctly with retry
over entire type1 routes lookup

Change-Id: I836451c7e4f2487f19850fe94cfdcefe1c3b1aca
Closes-Bug: 1777488

Jeba Paulaiyan (jebap)
tags: added: contrail-control
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.