Description of problem: When powering off VM with port mirroring enabled the VM id down in the UI but stuck in down state in vdsm vdsClient -s 0 list table ea37ce01-3203-44b9-8f87-36e5550a23b7 3458 golden_env_mixed_virtio_0 Down When running vdsClient -s 0 destroy ea37ce01-3203-44b9-8f87-36e5550a23b7 we get error Unexpected exception Thread-281::ERROR::2015-08-18 20:22:55,031::__init__::527::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 522, in _serveRequest res = method(**params) File "/usr/share/vdsm/rpc/Bridge.py", line 277, in _dynamicMethod result = fn(*methodArgs) File "/usr/share/vdsm/API.py", line 337, in destroy res = v.destroy() File "/usr/share/vdsm/virt/vm.py", line 3757, in destroy result = self.doDestroy() File "/usr/share/vdsm/virt/vm.py", line 3775, in doDestroy return self.releaseVm() File "/usr/share/vdsm/virt/vm.py", line 3675, in releaseVm supervdsm.getProxy().unsetPortMirroring(network, nic.name) File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> **kwargs) File "<string>", line 2, in unsetPortMirroring File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) TrafficControlException: (22, 'RTNETLINK answers: Invalid argument', ['/usr/sbin/tc', 'qdisc', 'del', 'dev', u'ovirtmgmt', 'ingress']) The VM cannot run again on this host untill I reboot the host Version-Release number of selected component (if applicable): vdsm-4.17.2-1.el7ev.noarch rhevm-3.6.0-0.11.master.el6.noarch Steps to Reproduce: 1. Create VM 2. Create vNIC profile with port mirroring for ovirtmgmt network 3. Select the vNIC profile with the port mirroring for the VM 4. Start the VM 5. Power off the VM Actual results: VM is stuck in VDSM Expected results: VM is not stuck in VDSM
Created attachment 1064383 [details] vdsm, supervdsm and engine logs
*** Bug 1255106 has been marked as a duplicate of this bug. ***
Verified on - 3.6.0-0.18.el6 with vdsm-4.17.8-1.el7ev.noarch