Bug 1143913

Summary:	CPU type is empty in the default cluster
Product:	[Retired] oVirt	Reporter:	Yevgeny Zaspitsky <yzaspits>
Component:	ovirt-engine-webadmin	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bugs, ecohen, gklein, lsurette, mgoldboi, michal.skrivanek, oourfali, pkubica, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 13:54:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yevgeny Zaspitsky 2014-09-18 08:58:43 UTC

Description of problem:


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


How reproducible: 


Steps to Reproduce:
1. Install a new ovirt
2. Add a host to the default cluster 
3.

Actual results:
Once the host is added the "CPU type" in edit cluster dialog is empty and non-editable.
Workaround: changing the CPU type field prior adding a host makes the field editable before and after host addition.

Expected results:
The "CPU type" field should not be empty and/or should be editable.

Additional info:

Comment 1 Omer Frenkel 2014-09-21 06:31:19 UTC

its ok that its empty, as it is detected from the first added host
but it should be editable..

Comment 2 Eldan Shachar 2014-10-26 06:42:46 UTC

CURRENT RELEASE

Comment 3 Petr Kubica 2014-11-03 07:24:21 UTC

Verified in 3.5.0.1-0.0.master.20141009085636.el6

Comment 5 Sandro Bonazzola 2015-11-04 13:54:28 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.