Description of problem: When opening the UI (Firefox), I'm getting the following exception on ui.log and the tree is not visible: 2017-03-29 02:09:45,621-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-17) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : a.i is undefined at org.ovirt.engine.ui.uicommonweb.models.SystemTreeModel.$executed(SystemTreeModel.java:415) at org.ovirt.engine.ui.uicommonweb.models.SystemTreeModel.executed(SystemTreeModel.java:415) at org.ovirt.engine.ui.frontend.Frontend$3.$onSuccess(Frontend.java:328) [frontend.jar:] at org.ovirt.engine.ui.frontend.Frontend$3.onSuccess(Frontend.java:328) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$3.$onSuccess(OperationProcessor.java:176) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$3.onSuccess(OperationProcessor.java:176) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:269) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:269) [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.onreadystatechange<(https://192.168.205.3/ovirt-engine/webadmin/?locale=en_US) 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.Du/<(https://192.168.205.3/ovirt-engine/webadmin/?locale=en_US) at Unknown.anonymous(Unknown) Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170328185427.gitb0842bf.el7.centos.noarch
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.
I am assuming this happened in a lago run. I have gotten a similar report from the community a while ago, and I was unable to reproduce it. There is something in your setup that the tree doesn't like. Can you give me some specifics on your setup? In particular any external providers or strange characters in the names of your DC/cluster/hosts? Also can you easily reproduce this, and if so can I have access to the machine to see?
(In reply to Alexander Wels from comment #2) > I am assuming this happened in a lago run. I have gotten a similar report > from the community a while ago, and I was unable to reproduce it. There is > something in your setup that the tree doesn't like. Can you give me some > specifics on your setup? Lago on my own laptop. Which may be a bit low on memory, but that's about it. Have you run Lago? > > In particular any external providers or strange characters in the names of > your DC/cluster/hosts? Also can you easily reproduce this, and if so can I > have access to the machine to see? Yes, Glance provider is in ovirt-system-tests, but not with any strange chars.
I have not run Lago at this point, can you reliably reproduce the issue in your lago run?
*** Bug 1438256 has been marked as a duplicate of this bug. ***
Also reported in Bug 1438256. Might not be anything to do with lago.
(In reply to Alexander Wels from comment #4) > I have not run Lago at this point, can you reliably reproduce the issue in > your lago run? Yes.
I don't think its lago, investigating bz1438256 let me to the new OVN provider. There are several issues with that, one being the URL/Type columns being switched in the row and 2 the column mapper in the backend code having some issue. This in turn creates an exception in the backend which results in bad data on the frontend which results in the exception and the missing system tree. Answering NO on installing the OVN provider solves the issue. @Yaniv, Can you setup lago to answer NO on the OVN provider in the engine-setup and see if that solves your issue? If so we need to get the owner of that feature to fix it.
(In reply to Alexander Wels from comment #8) > I don't think its lago, investigating bz1438256 let me to the new OVN > provider. There are several issues with that, one being the URL/Type columns > being switched in the row and 2 the column mapper in the backend code having > some issue. This in turn creates an exception in the backend which results > in bad data on the frontend which results in the exception and the missing > system tree. > > Answering NO on installing the OVN provider solves the issue. > > @Yaniv, > Can you setup lago to answer NO on the OVN provider in the engine-setup and > see if that solves your issue? If so we need to get the owner of that > feature to fix it. Lago (which you should learn to use - it's a great tool!), uses the default answers. What is the question I should add with NO?
(In reply to Yaniv Kaul from comment #9) > (In reply to Alexander Wels from comment #8) > > I don't think its lago, investigating bz1438256 let me to the new OVN > > provider. There are several issues with that, one being the URL/Type columns > > being switched in the row and 2 the column mapper in the backend code having > > some issue. This in turn creates an exception in the backend which results > > in bad data on the frontend which results in the exception and the missing > > system tree. > > > > Answering NO on installing the OVN provider solves the issue. > > > > @Yaniv, > > Can you setup lago to answer NO on the OVN provider in the engine-setup and > > see if that solves your issue? If so we need to get the owner of that > > feature to fix it. > > Lago (which you should learn to use - it's a great tool!), uses the default > answers. What is the question I should add with NO? --== STORAGE CONFIGURATION ==-- Install ovirt-provider-ovn(Yes, No) [Yes]?:No
(In reply to Alexander Wels from comment #10) > (In reply to Yaniv Kaul from comment #9) > > (In reply to Alexander Wels from comment #8) > > > I don't think its lago, investigating bz1438256 let me to the new OVN > > > provider. There are several issues with that, one being the URL/Type columns > > > being switched in the row and 2 the column mapper in the backend code having > > > some issue. This in turn creates an exception in the backend which results > > > in bad data on the frontend which results in the exception and the missing > > > system tree. > > > > > > Answering NO on installing the OVN provider solves the issue. > > > > > > @Yaniv, > > > Can you setup lago to answer NO on the OVN provider in the engine-setup and > > > see if that solves your issue? If so we need to get the owner of that > > > feature to fix it. > > > > Lago (which you should learn to use - it's a great tool!), uses the default > > answers. What is the question I should add with NO? > > --== STORAGE CONFIGURATION ==-- > > Install ovirt-provider-ovn(Yes, No) [Yes]?:No Lago is doing automated installation. I'll need to look at the answer file for this.
This is obviously is the workaround, but the bug should probably move to network to fix it the right way. Alexander - am I right?
Yes, I have 0 knowledge of that feature or why it is not working.
*** This bug has been marked as a duplicate of bug 1438467 ***