Juniper Openstack

  1. Bug #1552101
  2. Comment #18

Comment 18 for bug 1552101

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

Reviewed: https://review.opencontrail.org/18731
Committed: http://github.org/Juniper/contrail-vrouter/commit/eeaa761b982524b1e0984b91dc417c98fe4c52ed
Submitter: Zuul
Branch: R2.22.x

commit eeaa761b982524b1e0984b91dc417c98fe4c52ed
Author: Anand H. Krishnan <email address hidden>
Date: Wed Mar 2 12:12:07 2016 +0530

Do not reuse forwarding metadata post mirroring

A mirror action needs its own forwarding metadata since the forwarding
parameeters that are used for mirroring will be different from those
that are used for packet forwarding. In this particular case, the vrf
to which the packets are mirrored are different from the vrf to which
packets need to be classified, and hence the packets were dropped in the
flow module with no source route as the drop reason.

Change-Id: I21930818a5cdec560818acb79f671ce29ac8bc85
Closes-BUG: #1552101