Bug 1552656 - [4.1.11] Port Mirroring - Cannot shutdown a VM with port mirroring enabled network
Summary: [4.1.11] Port Mirroring - Cannot shutdown a VM with port mirroring enabled ne...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 2.1.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ovirt-4.1.11
: ---
Assignee: Edward Haas
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-07 13:35 UTC by Michael Burman
Modified: 2019-05-16 13:06 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-24 15:30:16 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Logs (848.92 KB, application/x-gzip)
2018-03-07 13:35 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1218 0 None None None 2018-04-24 15:30:22 UTC
oVirt gerrit 89297 0 ovirt-4.1 MERGED net: parse tc filter u32 chain number 2018-03-25 14:25:09 UTC
oVirt gerrit 89298 0 ovirt-4.1 MERGED net: Adjust tc filter show output parsing to fc27 2018-03-25 14:25:13 UTC

Description Michael Burman 2018-03-07 13:35:20 UTC
Created attachment 1405343 [details]
Logs

Description of problem:
[4.1.10] Port Mirroring - Cannot shutdown a VM with port mirroring enabled network.

If 2 VMs running with port mirroirng enabled networks, it's not possible to shutdown the second VM, it got stuck in unknown state untill rebooting the host!

We have new regression on 4.1.10.1 and i think this is on our side, because this is happens ONLY on 4.1.10 and rhel 7.5

rhel7.4 + 4.1.10 is OK
rhel7.5 + 4.2 is OK

2018-03-07 15:18:33,909+0200 ERROR (jsonrpc/2) [jsonrpc.JsonRpcServer] Internal server error (__init__:577)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 572, in _handle_request
    res = method(**params)
  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 202, in _dynamicMethod
    result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 332, in destroy
    res = v.destroy(gracefulAttempts)
  File "<string>", line 2, in destroy
  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method
    ret = func(*args, **kwargs)
  File "/usr/share/vdsm/virt/vm.py", line 4394, in destroy
    result = self.doDestroy(gracefulAttempts)
  File "/usr/share/vdsm/virt/vm.py", line 4412, in doDestroy
    return self.releaseVm(gracefulAttempts)
  File "/usr/share/vdsm/virt/vm.py", line 4295, in releaseVm
    nic.name)
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__
    return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, 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', ['/sbin/tc', 'qdisc', 'del', 'dev', 'pm1', 'ingress'])

Version-Release number of selected component (if applicable):
4.1.10.1-0.1.el7
vdsm-4.19.48-1.el7ev.x86_64
kernel-3.10.0-858.el7.x86_64

How reproducible:
100% on 4.1.10.1 + rhel7.5 only! 

Steps to Reproduce:
1. Start VM1 with port mirroring and start VM2 with port mirroring(same network)
2. Shutdown VM1
3. Try to shutdown VM2

Actual results:
Cannot shutdown VM2, host reboot is required!

Expected results:
Must work

- I couldn't find the 4.1.z version in the bugzilla

Comment 1 Red Hat Bugzilla Rules Engine 2018-03-07 16:16:34 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Yaniv Kaul 2018-03-08 12:53:34 UTC
Dan, RHEL 7.5 regression? Is it a blocker for 4.1.10?

Comment 3 Dan Kenigsberg 2018-03-12 13:36:18 UTC
Since it's fine with rhel-7.4 and it's fine with rhv-4.2 this should not be a blocker (even though I don't understand how this could happen).

Comment 4 Red Hat Bugzilla Rules Engine 2018-03-12 13:36:23 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 5 Eyal Edri 2018-03-13 09:57:33 UTC
agreed on last call this isn't a blocker+, moving to '?' to not block next build

Comment 6 Dan Kenigsberg 2018-03-13 10:29:07 UTC
I have no powers to set blocker-, so I am clearing the "regression" keyword instead.

Comment 8 Dan Kenigsberg 2018-03-19 14:07:58 UTC
Closing, since we did not solve this in 4.1.10, do not plan any 4.1.11, and this does not reproduce on 4.2.

Comment 12 Yaniv Lavi 2018-04-08 08:37:45 UTC
Adding keyword since this only impacts 4.1.z.

Comment 14 Michael Burman 2018-04-12 15:28:51 UTC
Bug can't reproduced. 
No regression introduced.

Verified on - 4.1.11.1-0.1.el7 and vdsm-4.19.51-1.el7ev.x86_64 using
kernel - 3.10.0-862.el7.x86_64
libvirt-daemon-3.9.0-14.el7_5.2.x86_64
libvirt-client-3.9.0-14.el7_5.2.x86_64

Comment 17 errata-xmlrpc 2018-04-24 15:30:16 UTC
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.

https://access.redhat.com/errata/RHBA-2018:1218

Comment 18 Franta Kust 2019-05-16 13:06:40 UTC
BZ<2>Jira Resync


Note You need to log in before you can comment on or make changes to this bug.