Bug 906378 - Dialog is closed unexpectedly if it is being opened after closing the previous dialog during progress.
Summary: Dialog is closed unexpectedly if it is being opened after closing the previou...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.5.0
Assignee: Einav Cohen
QA Contact: bugs@ovirt.org
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-31 14:39 UTC by Lior Vernia
Modified: 2016-02-10 19:45 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-22 09:37:46 UTC
oVirt Team: UX
Embargoed:


Attachments (Terms of Use)

Description Lior Vernia 2013-01-31 14:39:14 UTC
Description of problem:

When a popup dialog in the webadmin GUI triggers some asynchronous action, the dialog often becomes disabled and shows "loading" animation. If the action takes some time to finish, the user might get impatient and close the window. However, if they now reopen that window, and then the original action finished its operation and returns, the window will be closed unexpectedly.


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


How reproducible:

Always (as long as the action takes a while to finish).


Steps to Reproduce:
1. Install ovirt-engine afresh.
2. Enable VLAN tagging on management network.
3. Add host and storage to the system.
4. Setup host networks, edit management network, set boot protocol to static and check sync checkbox.
5. Confirm both windows and close the loading window.
6. Open setup host networks window again, and again edit management network. Wait for original action to return, and observe the disappearance of the host networks dialog.
  
Actual results:

When the setup networks command returns, the setup networks dialog closes, despite it being a different instance of the dialog.


Expected results:

The window should either be refreshed when the original action returns, or stay open without refreshing, but definitely not close.


Additional info:

This probably isn't a network problem, but rather a project-wide issue.

Comment 1 Itamar Heim 2013-12-01 08:49:14 UTC
still relevant?

Comment 2 Einav Cohen 2014-01-02 23:43:15 UTC
(In reply to Itamar Heim from comment #1)
> still relevant?

I assume it is; there is a chance that it would be extremely hard to solve / it is actually a consequence of a much bigger problem. Don't know when I will have time to look into it.

Comment 3 Itamar Heim 2014-01-12 08:41:29 UTC
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.

Comment 4 Itamar Heim 2014-06-22 09:37:46 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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