Description of problem: When trying to migrate a disk to another SD the web UI throws the following error: Cannot read property 'G' of null Here a log extract of ui.log: 2018-06-03 10:57:17,486+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-52) [] Permutation name: AEA766696E550914FBFDA5936BC98453 2018-06-03 10:57:17,486+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-52) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'G' of null at org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$lambda$1(DisksAllocationModel.java:107) at org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel$lambda$1$Type.onSuccess(DisksAllocationModel.java:107) at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:227) [frontend.jar:] at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:227) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:270) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:270) [frontend.jar:] at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) [gwt-servlet.jar:] at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) [gwt-servlet.jar:] at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) [gwt-servlet.jar:] at Unknown.eval(webadmin-0.js) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:275) [gwt-servlet.jar:] at Unknown.eval(webadmin-0.js) Version-Release number of selected component (if applicable): How reproducible: Just try to live migrate a vm disk Steps to Reproduce: 1. 2. 3. Actual results: Cannot read property 'G' of null Expected results: Disk migration should start Additional info:
Hi Arsene, I could not reproduce, does it happen for other disks in other VMs or just this specific one?
(In reply to Tal Nisan from comment #1) > Hi Arsene, > I could not reproduce, does it happen for other disks in other VMs or just > this specific one? HI Tal, This doesn't happen on all disks since I could migrate some of them, but now i have several disks I'm not able to migrate due to this error.
(In reply to Arsene Gschwind from comment #2) > (In reply to Tal Nisan from comment #1) > > Hi Arsene, > > I could not reproduce, does it happen for other disks in other VMs or just > > this specific one? > > HI Tal, > This doesn't happen on all disks since I could migrate some of them, but now > i have several disks I'm not able to migrate due to this error. I've tried to dig in the code to see what may cause this, seems like some disks might be missing, can you check the specific disks and see if all the images exist in the storage?
(In reply to Tal Nisan from comment #3) > (In reply to Arsene Gschwind from comment #2) > > (In reply to Tal Nisan from comment #1) > > > Hi Arsene, > > > I could not reproduce, does it happen for other disks in other VMs or just > > > this specific one? > > > > HI Tal, > > This doesn't happen on all disks since I could migrate some of them, but now > > i have several disks I'm not able to migrate due to this error. > > I've tried to dig in the code to see what may cause this, seems like some > disks might be missing, can you check the specific disks and see if all the > images exist in the storage? The image definitively exists since the VM are running and I'm able to see the disk on the storage. In the meantime I could migrate some disks using ovirt-shell but using the web ui still gives the same error.
Tried to reproduce in many different ways but unfortunately couldn't, since you've found a workaround and we don't have any clear information on what causes those specific disks to fail I'm closing this bug as insufficient data, please reopen if you have new information regarding