Created attachment 1236910 [details] vdsm log Description of problem: Unplugging the cable from the host, waiting for it to be non-responsive and then plugging it back VDSM is down with an error. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: vdsm jsonrpc.JsonRpcServer ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 547, 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 1410, in getAllVmIoTunePolicies io_tune_policies_dict = self._cif.getAllVmIoTunePolicies() File "/usr/share/vdsm/clientIF.py", line 447, in getAllVmIoTunePolicies vm_io_tune_policies[v.id] = {'policy': v.getIoTunePolicy(), File "/usr/share/vdsm/virt/vm.py", line 2730, in getIoTunePolicy io_tune = vmxml.find_first(qos, "ioTune", None) File "/usr/share/vdsm/virt/vmxml.py", line 110, in find_first return next(find_all(element, tag)) File "/usr/share/vdsm/virt/vmxml.py", line 89, in find_all if tag(element) == tag_: File "/usr/share/vdsm/virt/vmxml.py", line 148, in tag return element.tag AttributeError: 'NoneType' object has no attribute 'tag' Expected results: VDSM is up Additional info:
which precise vdsm.rpm is this?
(In reply to Dan Kenigsberg from comment #1) > which precise vdsm.rpm is this? Version : 4.20.0 Release : 38.git59c645a.fc24 From repo : ovirt-master-snapshot
I assume you meant network cable? wasn't sure about the impact here? is vdsm down afterwards and not coming up? thanks.
(In reply to Moran Goldboim from comment #3) > I assume you meant network cable? Yes :) > wasn't sure about the impact here? is vdsm down afterwards and not coming up? Right, it doesn't come up
I can't reproduce the problem (my host's network is only virtual after all) but I understand it can happen under certain circumstances and I believe the posted patch fixes it.
Arik, could you please verify the patch (http://gerrit.ovirt.org/69555) whether it fixes the problem?
(In reply to Milan Zamazal from comment #6) > Arik, could you please verify the patch (http://gerrit.ovirt.org/69555) > whether it fixes the problem? Yes, done.
Verified with rhevm-4.1.0.2-0.2.el7 and host: vdsm-4.19.2-2.el7ev.x86_64. host is nested and I was unplugging the virtual cable, so I hope this is enough, but don't see reason why behaviour should be different. After plugging back the network, host returned back to state 'up' and the error attached in the description doesn't appear.