Red Hat Bugzilla – Bug 1302236
Uncaught exception occurred. in the UI while choosing CPU Architecture as 'undefined' in the New Cluster dialog
Last modified: 2016-07-05 03:39:50 EDT
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):
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'.
Every time choosing and switching the CPU Architecture as 'undefined' from 'x86_64' or 'ppc64' an Uncaught exception occurred in the fronted UI.
Shouldn't invoke exception
Created attachment 1118713 [details]
Created attachment 1118714 [details]
Created attachment 1118715 [details]
Alona, shouldn't this be a network bug?
(In reply to Oved Ourfali from comment #4)
> Alona, shouldn't this be a network bug?
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.
rhevm-184.108.40.206-0.1.el7ev.noarch (build 4.0.0-19).
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.