Description of problem: On a setup containing a VM with port mirroring, restarting VDSM will result in traffic duplication on the NIC with port mirroring. Version-Release number of selected component (if applicable): vdsm-4.12.0-72.git287bb7e.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: A setup with 3 VMs on the same network. 1. Enable port mirroring on one of the VMs (using a profile with port mirroring on its VNIC) 2. Restart VDSM 3. Send traffic between the two VMs without port mirroring. 4. Monitor the traffic on the VM with port mirroring (for example using tcpdump on the interface with port mirroring). Actual results: The traffic between the two VMs without port mirroring will be duplicated on the monitoring machine. That is, each packet will be captured twice. Expected results: The traffic should not be duplicated. Additional info: Each subsequent restart to VDSM will increase the number of duplicate packets. To stop the duplication, one would need to unplug and plug the NIC with port mirroring.
Created attachment 791044 [details] vdsm log
Created attachment 791063 [details] supervdsm log
vdsm-4.12.0-170.el6ev.x86_64
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0040.html