Bug 1294087 - UI exception after editing of a storage domain in webadmin
Summary: UI exception after editing of a storage domain in webadmin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-3.6.2
: 3.6.2.5
Assignee: Tal Nisan
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-24 15:17 UTC by Tal Nisan
Modified: 2016-02-18 11:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:02:25 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
tnisan: devel_ack+
acanan: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 51061 0 master MERGED webadmin: Fix exception in edit storage model 2015-12-27 13:04:02 UTC
oVirt gerrit 51089 0 ovirt-engine-3.6 MERGED webadmin: Fix exception in edit storage model 2015-12-27 14:50:31 UTC
oVirt gerrit 51092 0 ovirt-engine-3.6.2 MERGED webadmin: Fix exception in edit storage model 2015-12-27 14:54:40 UTC

Description Tal Nisan 2015-12-24 15:17:28 UTC 
Description of problem:
When editing a storage domain in webadmin, a few seconds after the popup is close an exception alert appears

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


How reproducible:
100%

Steps to Reproduce:
1. Edit a storage domain, change a property and click "OK"
2.
3.

Actual results:
The popup is closed and a few seconds after an exception alert appears

Expected results:
No exception will be thrown

Additional info:
Comment 1 Aharon Canan 2016-01-18 10:36:41 UTC 
Verified
========
rhevm-3.6.2.5-0.1.el6.noarch
vdsm-4.17.17-0.el7ev.noarch

Steps to Reproduce:
===================
Edit a storage domain, change a property and click "OK"

Actual results:
===============
No exception alert appears
Note You need to log in before you can comment on or make changes to this bug.