Bug 835498 - Trying to remove DefaulQuota leads to webadmin window being locked forever (race, livelock?)
Summary: Trying to remove DefaulQuota leads to webadmin window being locked forever (r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Gilad Chaplik
QA Contact: Tomas Dosek
URL:
Whiteboard: sla
: 838301 (view as bug list)
Depends On:
Blocks: 818501
TreeView+ depends on / blocked
 
Reported: 2012-06-26 11:11 UTC by Tomas Dosek
Modified: 2016-02-10 20:16 UTC (History)
8 users (show)

Fixed In Version: SI12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:00:44 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot (79.26 KB, image/png)
2012-06-26 11:11 UTC, Tomas Dosek 		no flags Details
View All

Description Tomas Dosek 2012-06-26 11:11:11 UTC 
Created attachment 594432 [details]
Screenshot

Description of problem:
When User tries to remove default quota the remove popup windows locks forever.
See attached screenshot


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

How reproducible:
100 %

Steps to Reproduce:
1.In tree view select datacenter
2.Navigate to quota tab
3.Try to remove default quota
  
Actual results:
Lock of screen webadmin unsable until next reload of page

Expected results:
Error message should be displayed that default quota cannot be removed

Additional info: attaching screenshot
Comment 1 Gilad Chaplik 2012-07-02 14:22:09 UTC 
merged upstream (http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=9a2a291d4d6c856d443550fa879aac2ce45ff903)
Comment 2 Gilad Chaplik 2012-07-08 12:12:12 UTC 
*** Bug 838301 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Dosek 2012-07-30 11:54:03 UTC 
Verified - si12 - above described bug scenario no longer reproduces
Note You need to log in before you can comment on or make changes to this bug.