Description of problem: When creating new pool, after clicking on the OK button dialog with processing wheel is displayed until all VMs are created and attached to the pool. In the background is visible how the VM count is increasing by the pool item. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-4.2.0.2-0.1.el7.noarch How reproducible: always Steps to Reproduce: 1. have some template, go to Compute -> Pools 2. click on New, enter name, CPU type and count of VMs more than 10, that it takes some time to create 3. click on OK Actual results: dialog stays opened until all VMs are created Expected results: dialog closes immediately when the pool is created and VMs continue to create after Additional info: By removing pool is not the problem, the dialog closes immediately.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
This has been dragging for too long. Please retarget this to 4.2.7 as this is a regression and 100% reproducible
It's a regression from which version? 4.1? How did it behave there, the dialog closes right away?
(In reply to Raz Tamir from comment #2) > Please retarget this to 4.2.7 as this is a regression and 100% reproducible Why do you say it is a regression? Did it behave differently in the previous releases? We always created all the VMs for the pool before closing the dialog, only disks are created after that, just like for any regular VM. So I see this not as a regression, but as an improvement and it should be targeted 4.3.
It is really a regression. I tested it in 4.1.11 and 4.2.6 And maybe the word 'created' is misleading, better is 'assigned'. Sorry. See the attached videos.
Created attachment 1478920 [details] create pool 4.1.11
Created attachment 1478921 [details] create pool 4.2.6
Verified on : ovirt-engine-4.3.0-0.2.master.20181120211612.git51027b1.el7.noarch
*** Bug 1600061 has been marked as a duplicate of this bug. ***
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.