Currently, ServiceChain class does not use service list as a key.
As a result, if there are two policy rules with the same match condition,
but different service lists, we will keep on deleting one service chain
and creating another one. With this change, the two rules will result in
two separate service chains and they should be indpendently created and
deleted and should not interfere with each other.
Change-Id: If4009330d32ab885fb64cfe98adf551e00662c53
Closes-Bug: 1508044
(cherry picked from commit d091e66cfe4d7595fc1866c1289a5c5fa0f01719)
Reviewed: https:/ /review. opencontrail. org/18306 github. org/Juniper/ contrail- controller/ commit/ 5f5ae464d8b57a9 f29618ab1047245 cbcd170e5b
Committed: http://
Submitter: Zuul
Branch: R3.0
commit 5f5ae464d8b57a9 f29618ab1047245 cbcd170e5b
Author: Sachin Bansal <email address hidden>
Date: Mon Mar 7 17:22:44 2016 -0800
Use service list also as key for service chains
Currently, ServiceChain class does not use service list as a key.
As a result, if there are two policy rules with the same match condition,
but different service lists, we will keep on deleting one service chain
and creating another one. With this change, the two rules will result in
two separate service chains and they should be indpendently created and
deleted and should not interfere with each other.
Change-Id: If4009330d32ab8 85fb64cfe98adf5 51e00662c53 5fc1866c1289a5c 5fa0f01719)
Closes-Bug: 1508044
(cherry picked from commit d091e66cfe4d759