Bug 1011435 - NPE when updating a cluster compatibility version
Summary: NPE when updating a cluster compatibility version
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.3.0
Assignee: Tal Nisan
QA Contact: Tareq Alayan
URL:
Whiteboard: infra
: 1011458 1011594 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 09:26 UTC by Tal Nisan
Modified: 2016-02-10 19:01 UTC (History)
9 users (show)

Fixed In Version: is17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 19506 0 None None None Never
oVirt gerrit 19523 0 None None None Never

Description Tal Nisan 2013-09-24 09:26:09 UTC 
Description of problem:
When trying to update a cluster compatibility version engine throws an NPE

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


How reproducible:


Steps to Reproduce:
1. In webadmin edit a cluster with all hosts in maintenance status
2. Select a version other then the current one
3. Click OK

Actual results:
NPE is thrown in engine and "Internal engine error" message pops in the webadmin

Expected results:
Cluster version will be changed

Additional info:
Comment 1 Tal Nisan 2013-09-24 09:30:58 UTC 
Note that the cluster must have at least one host for the NPE to occur
Comment 3 Itamar Heim 2013-09-24 10:53:46 UTC 
*** Bug 1011458 has been marked as a duplicate of this bug. ***
Comment 4 Itamar Heim 2013-09-24 17:48:40 UTC 
*** Bug 1011594 has been marked as a duplicate of this bug. ***
Comment 5 Martin Pavlik 2013-10-03 08:53:19 UTC 
works in is17
Comment 6 Itamar Heim 2014-01-21 22:32:16 UTC 
Closing - RHEV 3.3 Released
Comment 7 Itamar Heim 2014-01-21 22:32:17 UTC 
Closing - RHEV 3.3 Released
Note You need to log in before you can comment on or make changes to this bug.