Bug 1463971 - [UI] - Cannot create new Host QoS entity via the DC flow
[UI] - Cannot create new Host QoS entity via the DC flow
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin (Show other bugs)
x86_64 Linux
high Severity high (vote)
: ovirt-4.2.0
: ---
Assigned To: Martin Sivák
Pavel Stehlik
: Regression
Depends On:
  Show dependency treegraph
Reported: 2017-06-22 03:51 EDT by Michael Burman
Modified: 2017-09-28 04:03 EDT (History)
3 users (show)

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

Attachments (Terms of Use)
ui log (25.10 KB, application/x-gzip)
2017-06-22 03:51 EDT, Michael Burman
no flags Details

  None (edit)
Description Michael Burman 2017-06-22 03:51:55 EDT
Created attachment 1290537 [details]
ui log

Description of problem:
[UI] - Cannot create new Host QoS entity via the DC flow.

When trying to create new host QoS entity via the DC > Host QoS > new flow, nothing happens when pressing ok and ui exception appears in the webadmin portal, in ui.log is see:

2017-06-22 10:42:02,700+03 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-3) [] Permutation name: 9A60D1A15790BDED8BC80587283CD2E9
2017-06-22 10:42:02,700+03 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-3) [] Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: (TypeError) : Cannot read property 'e' of undefined
        at java.lang.Throwable.Throwable(Throwable.java:70) [rt.jar:1.8.0_131]
        at java.lang.RuntimeException.RuntimeException(RuntimeException.java:32) [rt.jar:1.8.0_131]
        at com.google.web.bindery.event.shared.UmbrellaException.UmbrellaException(UmbrellaException.java:64) [gwt-servlet.jar:]
        at com.google.gwt.event.shared.UmbrellaException.UmbrellaException(UmbrellaException.java:25) [gwt-servlet.jar:]
        at com.google.gwt.event.shared.HandlerManager.$fireEvent(HandlerManager.java:117) [gwt-servlet.jar:]
        at com.google.gwt.user.client.ui.Widget.$fireEvent(Widget.java:127) [gwt-servlet.jar:]
        at com.google.gwt.user.client.ui.Widget.fireEvent(Widget.java:127) [gwt-servlet.jar:]
        at com.google.gwt.event.dom.client.DomEvent.fireNativeEvent(DomEvent.java:110) [gwt-servlet.jar:]
        at com.google.gwt.user.client.ui.Widget.$onBrowserEvent(Widget.java:163) [gwt-servlet.jar:]
        at com.google.gwt.user.client.ui.Widget.onBrowserEvent(Widget.java:163) [gwt-servlet.jar:]
        at com.google.gwt.user.client.DOM.dispatchEvent(DOM.java:1415) [gwt-servlet.jar:]
        at com.google.gwt.user.client.impl.DOMImplStandard.dispatchEvent(DOMImplStandard.java:312) [gwt-servlet.jar:]
        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)

When creating new Host QoS entity via the Networks > new Host QoS flow, everything working as it should and entity successfully created. 

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

How reproducible:

Steps to Reproduce:
1. Try to create new Host QoS from the DC

Actual results:
Nothing happens. ui exception in the ui.log

Expected results:
Should work as expected.
Comment 1 Michael Burman 2017-06-22 03:56:32 EDT
Same behaviour for STORAGE and VM QoS entities, but not for CPU.

Maybe it's should be moved to the UX team
Comment 2 Red Hat Bugzilla Rules Engine 2017-06-23 02:50:52 EDT
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.
Comment 3 Oved Ourfali 2017-07-19 08:33:09 EDT
Moving to SLA to check whether it works okay now, looking at all the flows.

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