Bug 1474304 - Exception during login of not existing property 'bh'
Exception during login of not existing property 'bh'
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin (Show other bugs)
All All
unspecified Severity medium (vote)
: ovirt-4.2.0
: ---
Assigned To: Greg Sheremeta
Pavel Stehlik
: Automation
Depends On:
  Show dependency treegraph
Reported: 2017-07-24 07:13 EDT by Lukas Svaty
Modified: 2017-07-24 09:00 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-24 09:00:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2+

Attachments (Terms of Use)

  None (edit)
Description Lukas Svaty 2017-07-24 07:13:15 EDT
Description of problem:
When trying to login inside tests to the webadmin portal we are hist by:

Operation cancelled: Error while executing action: A Request to the Server failed: The response could not be deserialized

Error while executing query: null

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. unknown

Actual results:
Not able to loggin, with traceback in logs.

Additional info:
2017-07-24 13:25:47,292+03 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-30) [] Permutation name: 7833486E7CB4A6E049BD84605D864F16
2017-07-24 13:25:47,292+03 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-30) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot 
read property 'bh' of null
        at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider.$lambda$4(AsyncDataProvider.java:376)
        at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider$lambda$4$Type.executed(AsyncDataProvider.java:376)
        at org.ovirt.engine.ui.frontend.Frontend$2.$onFailure(Frontend.java:332) [frontend.jar:]
        at org.ovirt.engine.ui.frontend.Frontend$2.onFailure(Frontend.java:332) [frontend.jar:]
        at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onFailure(OperationProcessor.java:184) [frontend.jar:]
        at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onFailure(OperationProcessor.java:184) [frontend.jar:]
        at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider.$handleMultipleQueriesFailure(GWTRPCCommunicationProvider.java:305) [frontend.jar:]
        at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onFailure(GWTRPCCommunicationProvider.java:263) [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)
Comment 1 Oved Ourfali 2017-07-24 07:23:40 EDT
Attaching complete logs is preferable.
Assigning to Greg.
Comment 2 Lukas Svaty 2017-07-24 07:24:15 EDT
the same exception is logged on logins, nothing else
Comment 4 Greg Sheremeta 2017-07-24 08:50:30 EDT
This is a gwt-rpc error, not actually related to login. I can see that the login is successful, the initial download compiles and runs, and gwt does several successful rpc calls before this failure.

It could be a bad installation. It could be a problem with the build. It's probably not a code problem, but I haven't ruled that out.

Can you try that exact same build on a different machine, so we can rule out the machine?
Comment 5 Lukas Svaty 2017-07-24 08:56:59 EDT
tried and I was able to successfully login, without any gwt errors
Comment 6 Lukas Svaty 2017-07-24 09:00:17 EDT
we discussed and investigated the environment with Greg, it does not reproduce on fresh installation, at the moment we are unable to track the issue here. We are closing this one with insufficient data for now, and reopen if this reappears

Note You need to log in before you can comment on or make changes to this bug.