Hide Forgot
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
Created attachment 1118713 [details] record
Created attachment 1118714 [details] screenshot
Created attachment 1118715 [details] symbolMap
Alona, shouldn't this be a network bug?
(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.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
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.
oVirt 4.0.0 has been released, closing current release.