Created attachment 839010 [details] log_collector Description of problem: user is not forced to unplug vNIC when switching to profile without port mirroring, which causes that port mirroring works despite vNIC is not supposed to be able to mirror the traffic Version-Release number of selected component (if applicable): user is not forced to unplug vNIC when switching to profile without port mirroring How reproducible: 100% Steps to Reproduce: 1. create network with 2 profiles (one profile with port mirroring on, second with port mirroring off) 2. create 3 VMs, each with 1 vNIC (VM1 with port mirroring profile attached, VM2 and VM3 with profile without port mirroring 3. start VMs 4. send traffic between VM2 and VM3 (VM1 should be able to mirror it) 5. switch vNIC on VM1 to profile with port mirroring disabled Actual results: VM1 is mirroring the traffic Expected results: user should be forced to unplug the vNIC on change from port mirroring profile to non mirroring so the change of mirroring state gets applied properly Additional info: 2013-12-19 15:23:52,451 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-6) [d844e] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Vnic Profile Network1 was renamed from Network1 to Network1_mirror.
This can be misleading to users, but I we agreed that changes to vNIC profiles take effect only on new VMs (or new vNICs), not on currently running ones. We may need to reconsider this decisions, but this bug should not block 3.3.0.
Moti corrects me: this bug is about changing the content of vNIC profile, but about switching a specific vNIC from one profile to another. That operation should indeed either change the specific vNIC or be blocked.
rhevm-3.3.0-0.42.el6ev.noarch
Closing - RHEV 3.3 Released