VrfEntry::Deletetimeout crash in contrail-vrouter-agent

[Manish Singh]

multicast route is not deleted as path is pending for TOR.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/8288
Submitter: Manish Singh (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/8288
Committed: http://github.org/Juniper/contrail-controller/commit/fde003d502002a72b60ee74eb6ed2f8bf29100bf
Submitter: Zuul
Branch: R2.1

commit fde003d502002a72b60ee74eb6ed2f8bf29100bf
Author: Manish <email address hidden>
Date: Wed Mar 11 13:41:54 2015 +0530

Problem: TOR path does not get deleted resulting in VRF delete timeout.

Description:
Consider a scenario where global vxlan identifier mode is changed and
along with this physical device vn entry is marked for deletion.
Meanwhile when multicast module receives delete notification for
physical_device_vn then vxlan id is picked from VN entry in physical_device_vn.
Multicast module picks up VXLAN from this VN deending on global vxlan mode.
Since global mode has changed vxlan picked up from VN and the one stored in
TOR olist of multicast will be different. This will result in failure for search
using physical_device/vxlan as key and path for TOR will not be deleted.

Fix: Store vxlan in state and at time of delete pick it up from state.

Change-Id: I41bee5ca14ca8556a1ffc14ede182e3dee0e2c8d
Closes-Bug: #1431143

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/8444
Submitter: Manish Singh (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/8444
Committed: http://github.org/Juniper/contrail-controller/commit/45800fea41c923b82a9ad90166b4bcd595a0e46b
Submitter: Zuul
Branch: master

commit 45800fea41c923b82a9ad90166b4bcd595a0e46b
Author: Manish <email address hidden>
Date: Wed Mar 11 13:41:54 2015 +0530

Problem: TOR path does not get deleted resulting in VRF delete timeout.

Description:
Consider a scenario where global vxlan identifier mode is changed and
along with this physical device vn entry is marked for deletion.
Meanwhile when multicast module receives delete notification for
physical_device_vn then vxlan id is picked from VN entry in physical_device_vn.
Multicast module picks up VXLAN from this VN deending on global vxlan mode.
Since global mode has changed vxlan picked up from VN and the one stored in
TOR olist of multicast will be different. This will result in failure for search
using physical_device/vxlan as key and path for TOR will not be deleted.

Fix: Store vxlan in state and at time of delete pick it up from state.

Change-Id: I41bee5ca14ca8556a1ffc14ede182e3dee0e2c8d
Closes-Bug: #1431143