Bug 1608093 - VM Portal white screen within a few seconds of initial render
Summary: VM Portal white screen within a few seconds of initial render
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-web-ui
Version: 4.2.4
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ovirt-4.3.0
: ---
Assignee: Greg Sheremeta
QA Contact: Lucie Leistnerova
Rolfe Dlugy-Hegwer
URL:
Whiteboard:
Depends On: 1609147
Blocks: 1638476
TreeView+ depends on / blocked
 
Reported: 2018-07-24 23:37 UTC by Jason
Modified: 2021-12-10 16:50 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, with some error conditions, the VM Portal displayed a completely white screen with no error message or debugging information. The current release fixes this issue: All error conditions display an error message and stack trace in the browser console.
Clone Of:
: 1638476 (view as bug list)
Environment:
Last Closed: 2019-05-08 12:35:10 UTC
oVirt Team: UX
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-web-ui issues 729 0 'None' 'closed' 'implement ErrorBoundary to prevent white screen crash' 2019-11-12 22:52:09 UTC
Red Hat Bugzilla 1599525 0 unspecified CLOSED ovirt-web-ui is not getting updating during engine-setup which is creating unexpected results 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1609147 0 high CLOSED [REST API] all VMs in VM Pool are returned to a pool user regardless of actual VM ownership 2021-12-10 17:00:54 UTC
Red Hat Issue Tracker RHV-44234 0 None None None 2021-12-10 16:50:43 UTC
Red Hat Product Errata RHBA-2019:1068 0 None None None 2019-05-08 12:35:16 UTC

Internal Links: 1599525 1609147

Description Jason 2018-07-24 23:37:00 UTC
Description of problem:

Site had their environment setup on 4.1.10 with some clusters on 4.0 and 4.1 mode. They then upgraded straight to 4.2 without upgrading the clusters or the RHV-M/Hosts to the latest minor release.

Once upgraded they noted that all users 1300'ish could see all VMs. They also noted that shortly (usually within 5 seconds) of a user logging in and seeing all the VMs the screen will "Flicker" and go blank (white) and nothing is visible. 

Site confirmed they are on the latest 1.3 version of the ovirt-web-ui.

How reproducible:

Everytime on this site.


Actual results:

see above

Expected results:

Users should only see the VMs assigned/created by them and the scree should not go blank.

Additional info:

This is an Extremely urgent with this site and may possibly be causing others issues.

Will attach logs shortly as well as details about the site/case.

Comment 7 Jason 2018-07-25 00:25:04 UTC
Also please see:

bz: 1599525

Comment 9 Michal Skrivanek 2018-07-25 04:58:30 UTC
(In reply to Jason from comment #7)
> Also please see:
> 
> bz: 1599525

But you say they have 1.3.9, so they do have the latest release ovirt-web-ui. 
ui.log is not relevant for VM portal, only for webadmin. Can you get a javascript console log from the browser?

Comment 10 Germano Veit Michel 2018-07-25 05:01:58 UTC
(In reply to Michal Skrivanek from comment #9)
> (In reply to Jason from comment #7)
> > Also please see:
> > 
> > bz: 1599525
> 
> But you say they have 1.3.9, so they do have the latest release
> ovirt-web-ui. 
> ui.log is not relevant for VM portal, only for webadmin. Can you get a
> javascript console log from the browser?

Hi Michal,

They have downgraded to 4.1 as they reached their deadline. 
I don't think anything was captured on the browser side. Greg or Travis are probably more aware than me, but I don't think additional data can be requested (and its all secure anyway, its hard to get any logs).

Comment 19 Germano Veit Michel 2018-07-26 04:57:15 UTC
How reproducible:
50% - Just the "See All VMs" part.
    - As discussed with Greg, the crash might be due to the huge amount of VMs they see.

Steps to Reproduce:
1. Install RHV 4.1.10
2. Create a Pool with 5 VMs
3. Add 2 AD users
4. Assign UserRole for both Users
5. Login with each user to User Portal, Grab a VM
6. Upgrade to 4.2
7. Login to VM Portal with one of the 2 AD users
   RESULT: user is able to see all 5 VMs, see screenshot
8. Update ovirt-web-ui to 1.3.9 (because this is left behind currently)
   RESULT: same thing, all 5 VMs of the pool can be seen

NOTE: user can also manipulate all VMs, including shutting down VMs from other users and get as many VMs as he wants.

Comment 22 Michal Skrivanek 2018-07-26 06:37:09 UTC
both users have UserRole set on System therefore they can see the same set of VMs - all of them

Comment 23 Germano Veit Michel 2018-07-26 06:41:31 UTC
(In reply to Michal Skrivanek from comment #22)
> both users have UserRole set on System therefore they can see the same set
> of VMs - all of them

Right, I configured both users with UserRole in RHV 4.1. When logging to the User Portal each could only see the Pool (not any VM), then get a VM from the Pool. At this point they would only see their VM.

After upgrading to 4.2, they don't see the "Pool" to request a VM from, but see all VMs of the Pool.

Is this really a permission problem? Is it the new portal? I'm very confused.

Comment 42 Greg Sheremeta 2018-08-24 19:17:34 UTC
Use this BZ 1608093 for the white screen.
Use BZ 1609147 for the pool permission issue.

Comment 43 Greg Sheremeta 2018-10-11 15:46:45 UTC
ovirt-web-ui 1.4.4 (ovirt 4.2.7) has a proper error screen instead of white screen of death. When an error is encountered, a helpful stack trace should print in the browser console.

Comment 47 Lucie Leistnerova 2019-02-25 16:33:35 UTC
Upgrade engine 4.1.11 -> 4.2.8 -> 4.3 (directly to 4.3 is not supported) was OK and user sees only his running VMs from the pool in VM portal. No blank page.
User was in group that had UserRole on the pool.

verified in ovirt-web-ui-1.5.0-1.el7ev.noarch with ovirt-engine-4.3.0.4-0.1.el7.noarch

Feel free to reopen, when the problem persist.

Comment 48 Rolfe Dlugy-Hegwer 2019-04-02 21:03:45 UTC
Updated the Doc Text field.

Comment 50 errata-xmlrpc 2019-05-08 12:35:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1068


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