Bug 1260782

Summary: None of the Host's emulated machine flags match the emulated machine flags supported at the cluster level.
Product: [Retired] oVirt Reporter: Anatoly Litovsky <tlitovsk>
Component: ovirt-engine-webadminAssignee: bugs <bugs>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6CC: abangsan, bugs, ecohen, fdeutsch, gklein, lsurette, mgoldboi, michal.skrivanek, mkalinin, rbalakri, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-08 10:58:11 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 Anatoly Litovsky 2015-09-07 17:44:35 UTC 
Description of problem:
Ovirt node cant be registered due to 
None of the Host's emulated machine flags match the emulated machine flags supported at the cluster level.

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


How reproducible:
100%

Steps to Reproduce:
1.auto install ovirt-node  from latest snapshot
2.press approve


Actual results:
None of the Host's emulated machine flags match the emulated machine flags supported at the cluster level.

Expected results:
Hoist approved

Additional info:
Node was build with latest centos packages.
Comment 3 Michal Skrivanek 2015-09-08 10:58:11 UTC 
as per offline discussion this is rhev engine and ovirt node
That's not supported
Comment 4 Marina Kalinin 2015-12-01 21:32:14 UTC 
Not sure what you meant, Michal, but I am having this problem now (maybe it is a different bug). I started hosted_engine setup, so that it detects hosts CPU type and flags automatically, but I cannot approve the host in the manager with this error. 3.6 beta1. 
rhevm-3.6.0.3-0.1.el6.noarch
Comment 5 Marina Kalinin 2015-12-02 01:14:28 UTC 
I opened this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1287299