Description of problem: Seen after hosted-engine installation in vdsm.log: 2018-03-18 07:06:01,556-0400 INFO (jsonrpc/5) [root] /usr/libexec/vdsm/hooks/after_vm_destroy/50_vhostmd: rc=0 err= (hooks:110) 2018-03-18 07:06:01,558-0400 INFO (jsonrpc/5) [api.virt] FINISH destroy return={'status': {'message': 'Machine destroyed', 'code': 0}} from=::ffff:192.168.200.99,41588, vmId=dac4bae1-1168-4cfd-81de-81bc88a16719 (api:52) 2018-03-18 07:06:01,558-0400 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call VM.destroy succeeded in 0.67 seconds (__init__:311) 2018-03-18 07:06:01,558-0400 ERROR (libvirt/events) [vds] Error running VM callback (clientIF:666) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 629, in dispatchLibvirtEvents v.onLibvirtLifecycleEvent(event, detail, None) AttributeError: 'NoneType' object has no attribute 'onLibvirtLifecycleEvent' Version-Release number of selected component (if applicable): [root@lago-he-basic-ansible-suite-master-host0 ~]# rpm -qa |grep vdsm vdsm-jsonrpc-4.30.0-158.git602f578.el7.centos.noarch vdsm-4.30.0-158.git602f578.el7.centos.x86_64 vdsm-network-4.30.0-158.git602f578.el7.centos.x86_64 vdsm-http-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-ethtool-options-4.30.0-158.git602f578.el7.centos.noarch vdsm-common-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-vhostmd-4.30.0-158.git602f578.el7.centos.noarch vdsm-python-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-fcoe-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-vfio-mdev-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-openstacknet-4.30.0-158.git602f578.el7.centos.noarch vdsm-api-4.30.0-158.git602f578.el7.centos.noarch vdsm-client-4.30.0-158.git602f578.el7.centos.noarch vdsm-hook-vmfex-dev-4.30.0-158.git602f578.el7.centos.noarch vdsm-yajsonrpc-4.30.0-158.git602f578.el7.centos.noarch
should be fixed in master and 4.2.3 by https://gerrit.ovirt.org/#/c/89346/
in 4.2 it's only fixed by https://gerrit.ovirt.org/#/c/89882/, so moving to MODIFIED now
*** Bug 1571115 has been marked as a duplicate of this bug. ***