Created attachment 1690539 [details] Added logs from engine and vdsm Description of problem: After editing a 4.2 cluster (even when i didn't change any setting) and saving the changes, it isn't possible to create a 4.2 VM in that cluster. When I try to create the VM (After filling at least the name field in it and saving it) I can't proceed (After pressing OK, the window doesn't close). In the engine log there is a NullPointerException exception in IsVmTemplateConflictsWithChipsetQuery.executeQueryCommand. Version-Release number of selected component (if applicable): RHV 4.4.0-36 with RHEL 8.2 installed on both engine and host How reproducible: 100% Steps to Reproduce: 1. Create a 4.2 compatibility data center and cluster, add a host and create and attach a data domain. 2. Edit the cluster (you don't have to change any settings) and save (press OK) 3. Try to create a VM on the same cluster (You can only write the VM name and press Ok) Actual results: Two first steps are working. In step 3, I fail to create the VM. In the browser's console I see the warning: "org.ovirt.engine.ui.frontend.Frontend WARNING: Failure while invoking runQuery [null, ]" In the engine log there's an error: "2020-05-21 09:59:20,113+03 ERROR [org.ovirt.engine.core.bll.IsVmTemplateConflictsWithChipsetQuery] (default task-29) [798f32ba-c829-4b47-996e-8087093848ee] Query 'IsVmTemplateConflictsWithChipsetQuery' failed: null 2020-05-21 09:59:20,113+03 ERROR [org.ovirt.engine.core.bll.IsVmTemplateConflictsWithChipsetQuery] (default task-29) [798f32ba-c829-4b47-996e-8087093848ee] Exception: java.lang.NullPointerException at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.IsVmTemplateConflictsWithChipsetQuery.executeQueryCommand(IsVmTemplateConflictsWithChipsetQuery.java:26) " Expected results: The VM is created successfully. Additional info:
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.