[2.20-3~icehouse] ECMP transparent-mode service chaining with linux Service VMs doesn't work

[Ganesha HV]

1]. Topo
=======
nodeb12(single node)

2] Setup
=======
              |-----svm1-----|
vn1-----|-----svm2-----|------vn2
              |-----svm3-----|

The svms are tinycore linux VMs.

3]. Observed a loop between the three SVMs and the following o/p is seen on the tcpdump :

22:49:56.075066 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075078 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075094 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075109 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075126 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075140 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075157 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075172 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075188 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075202 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
22:49:56.075219 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35
^C22:49:56.075234 STP 802.1d, Config, Flags [Topology change], bridge-id 8000.02:62:03:d1:2f:80.8001, length 35

Discussed with Anand.

This bug is preventing ecmp transparent service chaining case being added to ci_sanity.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10587
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10637
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/10587
Committed: http://github.org/Juniper/contrail-vrouter/commit/31a4cdaa173659023bd0c46ca0da7620110d8a16
Submitter: Zuul
Branch: master

commit 31a4cdaa173659023bd0c46ca0da7620110d8a16
Author: Divakar <email address hidden>
Date: Tue May 19 21:46:58 2015 -0700

Bum traffic handling in transparent service chain

When the BUM traffic is received on transparent service chain
interface, it has to be dropped to avoid the loops in that
service chain network.
Checking-in on behalf of Anand

Change-Id: Ic1b1a2f2c5716e2852582012963e6ee9934e9a1a
closes-bug: #1449166

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/10637
Committed: http://github.org/Juniper/contrail-vrouter/commit/617938c262d964eacb3ef2cffd41b4f9272034d7
Submitter: Zuul
Branch: R2.20

commit 617938c262d964eacb3ef2cffd41b4f9272034d7
Author: Divakar <email address hidden>
Date: Wed May 20 21:14:51 2015 -0700

Bum traffic handling in transparent service chain

When the BUM traffic is received on transparent service chain
interface, it has to be dropped to avoid the loops in that
service chain network.
Checking-in on behalf of Anand

Change-Id: Ife3c6087f90d7b93130d69652d4177da66162d91
closes-bug: #1449166

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10863
Submitter: Hari Prasad Killi (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10887
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10889
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10887
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10863
Submitter: Hari Prasad Killi (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10961
Submitter: Divakar Dharanalakota (<email address hidden>)

[Ganesha HV (ganeshahv)]

Checked and found to be working.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10961
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/10889
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/10961
Committed: http://github.org/Juniper/contrail-controller/commit/abdb26d0b61b759089b3572648394d16413e06ee
Submitter: Zuul
Branch: R2.20

commit abdb26d0b61b759089b3572648394d16413e06ee
Author: Divakar <email address hidden>
Date: Wed May 27 20:59:31 2015 -0700

Clearing service instance DB State after STOP command

If Delete of service instance is received before it was marked
unusable, to stop the namespace, StopServiceInstance command is issued,
which invokes the deletion of the namespace script. And immediately after
this, DB state is cleared. Clearing of DB State can result in deleting
of service instance DBEntry before namespace script completion. SIGCHILD
event after script completion looks for service instance that triggered the
task, and results in crash as the service isntance is already deleted.
To avoid crash, the DBState is cleared after processing the SIGCHILD
event. Also corresponding to the service instance, there can be many
tasks queued for execution. To identify how any SIGCHILDS to wait for,
running tasks cound is maintained in DBState. This could is manipulated
everytime the task is created, destroyed, error handled corresponding to
the service instance.

Testcases to follow in the next commit

Change-Id: I4b9853de271b8ee54016bb91b7a2e199cbce6b0d
closes-bug: #1449166
closes-bug: #1453956