Description of problem:
When trying to register a VM with snapshot the operation fails
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a VM with disks on a specific storage domain and take a snapshot
2. Move the domain containing the disks to maintenance and detach it
3. Re-attach the domain and try to register the VM
The VM registration fails
The VM registration should succeed
Re-opening the bug, I get an exception as soon as I try to import the VM from the storage domain that was placed in maintenance. This is with build rhevm-188.8.131.52-0.1. The UI error notes: "Uncaught exception occurred. Please try reloading the page."
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.
(In reply to Gilad Lazarovich from comment #1)
> Re-opening the bug, I get an exception as soon as I try to import the VM
> from the storage domain that was placed in maintenance. This is with build
> rhevm-184.108.40.206-0.1. The UI error notes: "Uncaught exception occurred. Please
> try reloading the page."
Please check again, there is a UI exception regardless to the function of the import which works as it should, I will open another bug on the UI exceptions (actually two different ones), this bug should be used only for the import a VM with snapshots
Import of VM with snapshot from an imported data domain works as expected.
I get Uncaught exceptions in UI:
SEVERE: Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: (TypeError)
__gwt$exception: <skipped>: b is null
But these are not in the scope of this bug as mentioned in comment #5 so don't block verification here.
Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.
For information on the release, and how to update to this release, follow the link below.
If the solution does not work for you, open a new bug report.