Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1600061

Summary: Create new vms pool - dialog window blocks UI
Product: [oVirt] ovirt-engine Reporter: Ilan Zuckerman <izuckerm>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.5.1CC: bugs, michal.skrivanek, mlehrer, rbarry
Target Milestone: ---Keywords: Performance
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-29 23:51:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ilan Zuckerman 2018-07-11 10:51:23 UTC 
Description of problem:
When creating a pool of 50-100 VMs, the "New pool" dialog window get stuck with a spinner for a long time.
50 VMs: 44 sec
100 VMs: 1 min 27 sec

Version-Release number of selected component (if applicable):
ovirt 4.2.5-0.1.el7ev

How reproducible:
Allways

Steps to Reproduce:
1. Compute --> pools --> new
2. in dialog box choose template and other necessary fields. Number of vms: 50 and 100 respectively.
3. click ok

Actual results:
When creating a pool of 50 vms: Dialog box gets stuck with spinning wheel for 44 sec, preventing from user making any other actions.
The same behavior when creating pool with larger amount of vms (100): this time we get stuck for as long as 1 min 27 sec

Expected results:
User shouldn't be blocked from using WebAdmin portal for other purposes while the pool is being created.

Additional info:
Attaching the following (google drive link in private message):
2 videos documenting the behavior.
log collector archive

Topology:
HE with one physical host
FC storage
Comment 2 Ryan Barry 2018-11-29 23:51:54 UTC 

*** This bug has been marked as a duplicate of bug 1530616 ***