svc V1: ecmp doesnt work after increasing the scale out from 1 to 3

[Senthilnathan Murugappan]

Have initially configured the no of instances to be 1 and things were working fine
Then increased the no of instances from 1 to 3 and observed that the first service instance doesnt work.
Naveen had a look at the setup and has triaged the same.

[Naveen N (naveenn)]

Packet was trapped for ECMP resolve and agent treated this flow as evicted flow.
If packet is trapped with ECMP resolve we should treat as update.

2016-02-18 10:22:22.537 PktFlowErr: ECMP Resolve for flow index 160812 controller/src/vnsw/agent/pkt/pkt_flow_info.cc 1801

[OpenContrail Admin (ci-admin-f)]

FIx is being tested.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17796
Submitter: Naveen N (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17796
Committed: http://github.org/Juniper/contrail-controller/commit/fd4507d6b7fc11f6b61f2351a58b8835d2c2744d
Submitter: Zuul
Branch: R3.0

commit fd4507d6b7fc11f6b61f2351a58b8835d2c2744d
Author: Naveen N <email address hidden>
Date: Thu Feb 25 14:04:31 2016 +0530

* In case of ECMP resolve treat flow as update
1> In case of ECMP resolve, packet would be trapped for
flow setup, in that scenario only component index should
be changed.
2> When reverse flow gets reused due to flow movement treat
the flow as update, instead of eviction.
Closes-bug:#1546876

Change-Id: I44fe8a66114c65442d630ef9dd79f2042c6586a7

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/18109
Submitter: Praveen K V (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit d302707ef3dd8af178f00dda9cf421318b9cd053
Author: Naveen N <email address hidden>
Date: Thu Feb 25 14:04:31 2016 +0530

* In case of ECMP resolve treat flow as update
1> In case of ECMP resolve, packet would be trapped for
flow setup, in that scenario only component index should
be changed.
2> When reverse flow gets reused due to flow movement treat
the flow as update, instead of eviction.

(cherry picked from commit 58f71adb3b91d1efff3dec06ff72bc69c8a9d326)
Closes-bug:#1546876
Change-Id: I44fe8a66114c65442d630ef9dd79f2042c6586a7