Juniper Openstack

Mirror metadata is not overwritten after changing the mirroring config on the port

Bug #1673735 reported by Shashikiran H
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.2
Fix Committed
Undecided
Divakar Dharanalakota
Juniper Openstack r3.2.3.0
Trunk
Fix Committed
Undecided
Divakar Dharanalakota
Juniper Openstack r4.0.0.0-fcs "r4.0.0.0"

Bug Description

Could be a followup/duplicate of Bug #1673688
Version: 3.2.1.0-26
Topo: Single node

My port already has metadata set in the vif entry even though it shouldn't(see Bug 1673688):
            Ingress Mirror Metadata: 3 1a 64 65 66 61 75 6c 74 2d 64
                                     6f 6d 61 69 6e 3a 64 65 6d 6f 3a
                                     73 6f 75 72 63 65 ff 0
            Egress Mirror Metadata: 4 1a 64 65 66 61 75 6c 74 2d 64 6f
                                    6d 61 69 6e 3a 64 65 6d 6f 3a 73
                                    6f 75 72 63 65 ff 0

I configure a mirroring entry for this port with mirror destination as a completely new vm and to mirror only ingress packets. This metadata still does not change:

            Ingress Mirror Metadata: 3 1a 64 65 66 61 75 6c 74 2d 64
                                     6f 6d 61 69 6e 3a 64 65 6d 6f 3a
                                     73 6f 75 72 63 65 ff 0
            Egress Mirror Metadata: 4 1a 64 65 66 61 75 6c 74 2d 64 6f
                                    6d 61 69 6e 3a 64 65 6d 6f 3a 73
                                    6f 75 72 63 65 ff 0

See original description
Tags: vrouter
Shashikiran H (skiranh)
description: updated
jayaramsatya (jayaramsatya)
Changed in juniperopenstack:
assignee: jayaramsatya (jayaramsatya) → Divakar Dharanalakota (ddivakar)
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

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

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

Reviewed: https://review.opencontrail.org/30248
Committed: http://github.org/Juniper/contrail-vrouter/commit/fb65fa77d796342d68d63fdc5016eb8f03c49ad1
Submitter: Zuul (<email address hidden>)
Branch: master

commit fb65fa77d796342d68d63fdc5016eb8f03c49ad1
Author: Divakar D <email address hidden>
Date: Fri Apr 7 16:50:26 2017 +0530

Update the mirror metadata len correctly

While making the Sandesh interface request structure from the VIF,
mirror metadata len is not getting initizlised to zero if mirror meta
data does not exist. This is leading to previous metadata len being used
for the current metadata and display of old metadata.

As a fix, metadata length is always initialised to zero before updating
it.

Change-Id: I8ddbdf669abeec47be9f7be021f59c39cf3f0d2d
closes-bug: #1673735

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.2

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

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

Reviewed: https://review.opencontrail.org/30313
Committed: http://github.org/Juniper/contrail-vrouter/commit/c719e068f66035fd122ebd1b13d9d9f11cc0dd7c
Submitter: Zuul (<email address hidden>)
Branch: R3.2

commit c719e068f66035fd122ebd1b13d9d9f11cc0dd7c
Author: Divakar D <email address hidden>
Date: Fri Apr 7 16:50:26 2017 +0530

Update the mirror metadata len correctly

While making the Sandesh interface request structure from the VIF,
mirror metadata len is not getting initizlised to zero if mirror meta
data does not exist. This is leading to previous metadata len being used
for the current metadata and display of old metadata.

As a fix, metadata length is always initialised to zero before updating
it.

Change-Id: I8ddbdf669abeec47be9f7be021f59c39cf3f0d2d
closes-bug: #1673735
(cherry picked from commit fb65fa77d796342d68d63fdc5016eb8f03c49ad1)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.