Description of problem: When exporting the VM (the "new" export button), the following exception occurs: null: java.lang.NullPointerException at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImagesHandler.shouldUseDiskBitmaps(ImagesHandler.java:1122) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupVolumesDataCommand.copyVolumeData(CopyImageGroupVolumesDataCommand.java:141) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupVolumesDataCommand.performNextOperation(CopyImageGroupVolumesDataCommand.java:111) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) How reproducible: always Steps to Reproduce: 1. Create a VM with a disk 2. Click the export button 3. Fill in the form and confirm Actual results: The export fails Expected results: The export should succeed Additional info: The exception occurs in ImagesHandler::shouldUseDiskBitmaps method. It was probably introduced with the following patch: https://gerrit.ovirt.org/#/c/ovirt-engine/+/114561/3/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/disk/image/ImagesHandler.java
How is this export different from the export test in OST?
in OST we test exporting a VM to an OVA this functionality seems different as you select a target storage domain - it's probably not really about exporting the VM but rather ensuring the vm configuration and its disks reside on the target storage domain I suppose
Lucia, Are you trying to export the VM to an export domain or to a data domain? Also, please attach engine logs.
(In reply to Eyal Shenitzky from comment #3) > Lucia, > > Are you trying to export the VM to an export domain or to a data domain? > > Also, please attach engine logs. Another thing is that fix for bug 1954447 merged only to 4.4.7 and not 4.4.6. Can you please confirm the engine version?
Lucia, Can you pls share on which storage domain type the VM's disks reside? What is the target storage domain type? Did you try to export with/without collapse snapshots? Thanks
Created attachment 1781670 [details] Engine log.
Sorry, I selected the last available release, but I am experiencing it on master. I've removed the "Version" now. I exported from Data master (NFS) to another Data (NFS). It works with Collapse snapshots checked, but fails if it is unchecked (that is the default option in the dialog).
Just to clarify in rhv-4.4.6 (RC/0day) this was tested and works. It was broken in master meaning it's broken in 4.4.7 only.
(In reply to Avihai from comment #8) > Just to clarify in rhv-4.4.6 (RC/0day) this was tested and works. > > It was broken in master meaning it's broken in 4.4.7 only. thanks for confirmation
Verified on ovirt-engine-4.4.7-0.23.el8ev.noarch.
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.7 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.