Bug 1340937
| Summary: | Selecting 'Errata' System tree node while on Dashboard tab makes GUI partially stuck or totally unresponsive (browser dependent) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine-dashboard | Reporter: | Pavel Novotny <pnovotny> | ||||
| Component: | Core | Assignee: | Alexander Wels <awels> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Novotny <pnovotny> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | awels, gklein, oourfali | ||||
| Target Milestone: | ovirt-4.0.0-rc | Keywords: | Performance | ||||
| Target Release: | 1.0.0 | Flags: | rule-engine:
ovirt-4.0.0+
rule-engine: blocker+ rule-engine: planning_ack+ rule-engine: devel_ack+ pnovotny: testing_ack+ |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-05 08:02:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1324860 | ||||||
| Attachments: |
|
||||||
This appears to happen when you switch from the dashboard to any item in the tree that results in just the one main tab being shown (like errata, or providers, or any of the leaf nodes). I suspect it has something to do with the logic that hides the dashboard tab and the other tabs. Still investigating. (In reply to Alexander Wels from comment #1) > This appears to happen when you switch from the dashboard to any item in the > tree that results in just the one main tab being shown (like errata, or > providers, or any of the leaf nodes). I suspect it has something to do with > the logic that hides the dashboard tab and the other tabs. Still > investigating. Regarding the only main tab shown - I found out that the Dashboard main tab disappears only after you explicitly select the root System tree node and then something else from the tree. But this is more related to bug 1340928. The subject of this bug still stands - if you select the Errata tree node as the first thing, then only Errata main tab is shown and the GUI becomes unusable from that point on. Yes, I have a patch pending review that will fix this issue. Verified in ovirt-engine-dashboard-1.0.0-20160615git43298a4.el7ev.x86_64 rhevm-4.0.0.6-0.1.el7ev.noarch (build 4.0.0-19). Verified according to reproducer from comment 0. After clicking on Errata tree item, the UI remains responsive. The Errata main tab now immediately shows: "Problem retrieving errata: The engine is not associated with a Foreman/Satellite provider. No errata for the engine are available." which is correct. oVirt 4.0.0 has been released, closing current release. |
Created attachment 1162955 [details] engine.log Description of problem: While on Dashboard tab, clicking on Errata from System tree makes the GUI totally unresponsive (Chromium) or at least partially stuck (Firefox). Version-Release number of selected component (if applicable): ovirt-engine-4.1.0-0.0.master.20160529171307.git359707b.el7.centos.noarch ovirt-engine-dashboard-0.0.1-2.20160527git3bb1fe3.el7.centos.noarch Browsers: Chromium 50.0.2661.102 Firefox 45.1.1 ESR (Mozilla) How reproducible: 100% Steps to Reproduce: 1. Make sure Dashboard tab is active. 2. Click on 'Errata' node from System tree on the left. 3. Actual results (see engine.log with described markers): a) Firefox: GUI seems to get stuck. But hovering over clickable elements shows pointer cursor for fraction of a second. With numerous double/tripple/etc. clicks on 'System' tree node you should be able to select it and "free" yourself and get back into usual "mode", where GUI responsiveness and functionality is restored. No spikes in CPU usage were observed here. b) Chromium: GUI becomes totally unresponsive. Clicking on anything has no effect. Also CPU usage goes up - 'top' stats: 0.9 before; 2.7 after 1 minute; 3.8 after 5 minutes (quad core i7-3520M CPU @ 2.90GHz, all cores utilized). Here, page reload is the only solution. Expected results: Following message is shown (in case no Foreman/Satellite provider is set up): "Problem retrieving errata: The engine is not associated with a Foreman/Satellite provider. No errata for the engine are available." Additional info: Firefox seemed to handle this situation somehow, but for Chromium this is a one-click showstopper. ui.log does not contain any ERROR/WARN messages.