Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sorry, I mistakenly opened the bug without entering description. Description of problem: While trying to remove USB passthrough device from VM, an engine NPE occurs and the devices failed to be removed: 2018-03-18 16:51:19,731+02 ERROR [org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand] (default task-27) [4c2992e6-4627-40ad-b23d-3a2e59b42166] Exception: java.lang.N ullPointerException This issue is not relevant for PCI device. Refreshing host capabilities is not solving this issue. Version-Release number of selected component (if applicable): rhvm-4.2.2.4-0.1.el7 vdsm-4.20.22-1.el7ev.x86_64 libvirt-client-3.9.0-14.el7.x86_64 qemu-kvm-rhev-2.9.0-16.el7_4.15.x86_64 How reproducible: 100% Steps to Reproduce: 1. Attach USB device to VM. Run VM and verify USB device is attached. 2. Power off VM. 3. Try to remove USB device (from Webadmin -> Compute -> VMs -> click VM -> host devices tab) Actual results: USB failed to be removed and the next Webadmin error appears: Operation Canceled Error while executing action RemoveVmHostDevices: Internal Engine Error Expected results: USB device should be removed. Additional info: vdsm.log and engine.log (2018-03-18 17:02:49,795+02 ERROR) attached.
Created attachment 1409507 [details] engine.log
Created attachment 1409508 [details] vdsm.log
Verification version: rhvm-4.2.2.5-0.1.el7 vdsm-4.20.23-1.el7ev.x86_64 qemu-kvm-rhev-2.10.0-21.el7_5.1.x86_64 libvirt-client-3.9.0-14.el7_5.2.x86_64 Verification steps: 1. Attach USB device and PCI device to RHEL VM. Run VM and verify devices are attached and function. 2. Power off VM. 3. Browse Webadmin -> VM -> host devices, select all devices and click "remove device" button. 4. Verify devices removed from VM. 5. Repeat steps 1-4 on Windows BM
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.