Bug 834302

Summary:	edit cluster shows intel conroe instead when cluster is empty
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Itamar Heim <iheim>
Component:	ovirt-engine	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yaniv Kaul <ykaul>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, dyasny, hateya, iheim, jkt, lpeer, ofrenkel, Rhev-m-bugs, yeylon, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	SI10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 20:01:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Itamar Heim 2012-06-21 13:24:19 UTC

an empty cpu name for the default cluster will allow the first host added to it to set the cluster cpu name.
need to make sure this only happens in clean install, and does not change the cpu name for an installed system (i.e., may be worth to fix the original script creating this, rather than a regular upgrade file)

Comment 2 Itamar Heim 2012-06-21 19:27:26 UTC

actually it is a bug...
the db does have it empty, just the UI shows the first entry instead of an empty entry

select cpu_name from vds_groups;
 cpu_name 
----------
 
(1 row)

Comment 3 Itamar Heim 2012-06-24 15:30:25 UTC

*** Bug 664422 has been marked as a duplicate of this bug. ***

Comment 4 Shahar Havivi 2012-06-25 12:23:16 UTC

post at: http://gerrit.ovirt.org/#/c/5674/

Comment 5 Yaniv Kaul 2012-07-05 11:57:55 UTC

SI9.1:
When creating a new cluster, you HAVE to specify a CPU level (whereas I'd expect the first host to set it). Is this the expected behavior?
It does show a default of empty, but you have to pick one to create the cluster object.

Comment 6 Shahar Havivi 2012-07-05 13:14:14 UTC

(In reply to comment #5)
> SI9.1:
> When creating a new cluster, you HAVE to specify a CPU level (whereas I'd
> expect the first host to set it). Is this the expected behavior?
> It does show a default of empty, but you have to pick one to create the
> cluster object.

you are creating a new cluster that have no host.

Comment 7 Yaniv Kaul 2012-07-05 13:48:31 UTC

(In reply to comment #6)
> (In reply to comment #5)
> > SI9.1:
> > When creating a new cluster, you HAVE to specify a CPU level (whereas I'd
> > expect the first host to set it). Is this the expected behavior?
> > It does show a default of empty, but you have to pick one to create the
> > cluster object.
> 
> you are creating a new cluster that have no host.

Indeed, and I was hoping the first host to join would determine the CPU level.
Adding a host is the next step in the wizard.

Comment 10 Haim 2012-08-07 06:24:15 UTC

verified on si13:

- cluster CPU for default cluster after clean install is determined by host cpu vendor.
- new cluster is set with empty cpu.