Bug 1530961

Summary:	request to remove a pool selects other one in the list
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	Frontend.WebAdmin	Assignee:	Alexander Wels <awels>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Necpal <dnecpal>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	awels, bugs, dnecpal, lsvaty, michal.skrivanek, tjelinek
Target Milestone:	ovirt-4.2.2	Keywords:	Regression
Target Release:	4.2.2.2	Flags:	tjelinek: ovirt-4.2? rule-engine: blocker? tjelinek: planning_ack? tjelinek: devel_ack+ lsvaty: testing_ack+
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:	2018-03-29 11:00:17 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:

Description Lucie Leistnerova 2018-01-04 10:17:33 UTC

Description of problem:
By removing a pool other one (the first) in the list is selected after the dialog closes, but the pool is still displayed in the list, waiting to remove all attached VMs.

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 a template, create 3 pools (one of them with more than 5 VMs, name it so that it will not be the first in the list)
2. wait untill all VMs are created
3. remove the pool with 5 VMs

Actual results: pool is still in the list, but selected is the first one


Expected results: pool stays selected and selection changes after it is really removed from the list

Comment 1 Tomas Jelinek 2018-01-09 08:56:57 UTC

@Alex: is this fixed by https://gerrit.ovirt.org/#/c/85965/ or is this a different case?

Comment 2 Alexander Wels 2018-01-09 13:19:39 UTC

No it is not, I will have to think about how to solve this as its hard to detect that the operation to remove the pool finished. Basically the call to remove immediately returns success due to it being an asynchronous operation. Then later at some point the grid is refreshed with the actual pool removed. The problem is what do we do in the mean time. We can keep the current selected, but then when the grid is refreshed we lose the selection because the current selection is no longer in the grid. So as a general solution I select the next one (which is what is prompting all these the next one is selected on an error bugs). In this case there is no error and thus selecting the next one is somewhat valid, but since the operation takes a long time it is weird.

I am going to have to think about this a little bit.

Comment 3 Red Hat Bugzilla Rules Engine 2018-01-10 07:59:24 UTC

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.

Comment 4 David Necpal 2018-03-07 13:47:00 UTC

Verified on version: Software Version: 4.2.2.2-0.1.el7

Comment 5 Sandro Bonazzola 2018-03-29 11:00:17 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.