Created attachment 1419149 [details] engine and vdsm logs Description of problem: Start a VM fails with NPE in PPC env in case the VM has a sPAPR VSCSI disk attached Version-Release number of selected component (if applicable): rhvm-4.2.2.6-0.1.el7.noarch vdsm-4.20.23-1.el7ev.ppc64le libvirt-3.9.0-14.el7_5.2.ppc64le qemu-kvm-rhev-2.10.0-21.el7_5.1.ppc64le How reproducible: Always Steps to Reproduce: 1. Create a VM and attach a sPAPR VSCSI disk to it 2. Start the VM Actual results: Start VM fails 2018-04-09 11:23:52,242+03 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-4466) [afcb7856-ce05-4907-8d05-37840c1fa871] Failed to create VM: java.lang.NullPointerE xception at org.ovirt.engine.core.vdsbroker.builder.vminfo.VmInfoBuildUtils.calculateAddressForScsiDisk(VmInfoBuildUtils.java:1241) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDisks(LibvirtVmXmlBuilder.java:1147) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:967) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:237) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:112) [vdsbroker.jar:] Expected results: Start VM should succeed Additional info:
Arik, can you take a look?
Does it work with CL 4.1?
Seems related to [1]. Sharon, please check this. [1] https://gerrit.ovirt.org/#/c/88065/
Created attachment 1419909 [details] 4.1 cluster Yaniv - The bug does reproduce on 4.1 cluster. Logs attached. Sharon - In the engine.log attached it is the case since that's the way I've reproduced the issue. The bug is reproduced also with a simpler scenario of creating a VM with no disks, attach a SPAPR_VSCSI disk to it and start it.
reducing severity because this is a pre-existing bugs no one reported for a long time
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.
(In reply to Michal Skrivanek from comment #8) > reducing severity because this is a pre-existing bugs no one reported for a > long time Michael, this test passed on previous 4.2 builds, the last PPC RHV automation execution that this case passed was on 4.2.2-7 from March 24.
Ah, so Sharon asked about that earlier and the answer was indicating otherwise. Ok then
Verify with: Engine: 4.2.3.2-0.1.el7 Host: OS Version:RHEL - 7.5 - 8.el7 Kernel Version:3.10.0 - 862.el7.ppc64le KVM Version:2.10.0 - 21.el7_5.2 LIBVIRT Version:libvirt-3.9.0-14.el7_5.3 VDSM Version:vdsm-4.20.26-1.el7ev Steps: 1. Create a VM and attach a sPAPR VSCSI disk to it 2. Start the VM VM started
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 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.