Bug 1463211

Summary: Pop up event messages scattered around the top of the screen in case of multiple events
Product: [oVirt] ovirt-engine Reporter: Eyal Shenitzky <eshenitz>
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, eshenitz, gshereme, lleistne, lsvaty, oourfali
Target Milestone: ovirt-4.2.0Flags: gshereme: needinfo-
rule-engine: ovirt-4.2+
Target Release: ---   
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: 2017-12-20 10:56:05 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:
Attachments:
Description Flags
Screen shot
none
vertical stacked notifications none

Description Eyal Shenitzky 2017-06-20 11:40:37 UTC 
Description of problem:
When having updates for multiple events on the same time, they appear on the top of the screen without consistent order.  

Version-Release number of selected component (if applicable):
engine - 4.2.0-0.0.master.20170618184152.gitb0f84a1.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create VM with multiple disks at the same size
2. Move the VM's disks to different storage domain

Actual results:
At the end of the migration, if the operations finish at the same time, pop-up events shown on the top of the screen without consistent order  

Expected results:
The event pop-up should appear as list/ order by the time

Additional info:
Comment 1 Oved Ourfali 2017-06-21 12:46:09 UTC 
Can you give a screenshot of that?
I saw those in order, but perhaps I missed something.
Comment 2 Eyal Shenitzky 2017-06-25 12:04:37 UTC 
Created attachment 1291698 [details]
Screen shot
Comment 3 Eyal Shenitzky 2017-06-25 12:05:55 UTC 
I think it will be better to show the pop-ups on the bottom of the screen, the are fewer buttons / information that will cover
Comment 4 Greg Sheremeta 2017-06-25 15:10:13 UTC 
(In reply to Eyal Shenitzky from comment #3)
> I think it will be better to show the pop-ups on the bottom of the screen,
> the are fewer buttons / information that will cover

The pattern is for them to be on top -- and I like them up top, as well.
http://www.patternfly.org/pattern-library/communication/toast-notifications/

Re: the bug, listing them out horizontally is a bug.

Should multiple notifications stack on top of each other vertically as they happen, or should we show only one at a time (like a stack of cards)?
Comment 5 Alexander Wels 2017-06-26 11:35:50 UTC 
Created attachment 1291950 [details]
vertical stacked notifications

As you can see the notification should start at top right, and then stack as in the screenshot. Maybe you need to clear your cache?
Comment 6 Greg Sheremeta 2017-06-26 20:33:22 UTC 
@Eyal, what version of Chrome is that? Please update to the latest, clear cache, and retry.
Comment 7 Eyal Shenitzky 2017-06-29 06:31:34 UTC 
chrome version was - Version 56.0.2924.87 (64-bit)
As far as I know this is the latest version for fedora
Comment 8 Oved Ourfali 2017-08-29 12:25:10 UTC 
Lukas, does it reproduce for QE?
Comment 9 Lucie Leistnerova 2017-08-29 14:06:22 UTC 
I did not reproduce it, all notifications appeared in top right corner below each other as is shown in Alexanders attachment. I have tested 
ovirt-engine-4.2.0-0.0.master.20170828065003.git0619c76.el7.centos.noarch
in Google Chrome 60.0 and Firefox 55.0.1 on Fedora 26.
Comment 10 Oved Ourfali 2017-08-29 15:06:44 UTC 
moving to VERIFIED.
I hope clearing the cache will fix it if you still have issues.
Comment 11 Sandro Bonazzola 2017-12-20 10:56:05 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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