Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1302236

Summary: Uncaught exception occurred. in the UI while choosing CPU Architecture as 'undefined' in the New Cluster dialog
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Greg Sheremeta <gshereme>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Novotny <pnovotny>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.2.6CC: alkaplan, bugs, oourfali, sbonazzo
Target Milestone: ovirt-4.0.0-betaFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 4.0.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 07:39:50 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:
Attachments:
Description Flags
record
none
screenshot
none
symbolMap none

Description Michael Burman 2016-01-27 09:29:14 UTC 
Description of problem:
Uncaught exception occurred. in the UI while choosing CPU Architecture as 'undefined' in the New Cluster dialog. 

The exception occurred in the [New Cluster] dialog, when choosing/switching the CPU Architecture as 'undefined' from 'x86_64' or 'ppc64'. 

Version-Release number of selected component (if applicable):
3.6.2.6-0.1.el6

How reproducible:
100

Steps to Reproduce:
1. Under [Clusters] main tab press New Cluster and choose CPU Architecture as 'x86_64', then switch back to 'undefined'. Switch to 'x86_64' and switch back to 'undefined'.

Actual results:
Every time choosing and switching the CPU Architecture as 'undefined' from 'x86_64' or 'ppc64' an Uncaught exception occurred in the fronted UI. 

Expected results:
Shouldn't invoke exception
Comment 1 Michael Burman 2016-01-27 09:35:29 UTC 
Created attachment 1118713 [details]
record
Comment 2 Michael Burman 2016-01-27 09:40:06 UTC 
Created attachment 1118714 [details]
screenshot
Comment 3 Michael Burman 2016-01-27 09:40:56 UTC 
Created attachment 1118715 [details]
symbolMap
Comment 4 Oved Ourfali 2016-01-29 16:55:15 UTC 
Alona, shouldn't this be a network bug?
Comment 5 Oved Ourfali 2016-02-03 11:32:58 UTC 
(In reply to Oved Ourfali from comment #4)
> Alona, shouldn't this be a network bug?

My bad.
I've put a needinfo on the wrong bug.
Comment 6 Sandro Bonazzola 2016-05-02 09:48:57 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 7 Pavel Novotny 2016-06-24 14:27:57 UTC 
Verified in 
rhevm-4.0.0.6-0.1.el7ev.noarch (build 4.0.0-19).
ovirt-engine-webadmin-portal-4.0.0.6-0.1.el7ev.noarch

Following reproducer in comment 0, I tried all the state transitions of the cluster CPU arch:
- undefined -> x86_64
- undefined -> ppc64
- x86_64 -> undefined
- ppc64 -> undefined
- ppc64 -> x86_64
- x86_64 -> ppc64

No UI exception has been thrown in any of the cases above.
Comment 8 Sandro Bonazzola 2016-07-05 07:39:50 UTC 
oVirt 4.0.0 has been released, closing current release.