Bug 1063829

Summary: automatic installation fails on "CPU type must be specified"
Product: [Retired] oVirt Reporter: Yaniv Bronhaim <ybronhei>
Component: ovirt-liveAssignee: Ohad Basan <obasan>
Status: CLOSED NOTABUG QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, eedri, gklein, iheim, sbonazzo, yeylon
Target Milestone: ---Keywords: UserExperience
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-20 11:44:14 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:
Attachments:
Description Flags
failed ovirt-engine installation none

Description Yaniv Bronhaim 2014-02-11 13:44:37 UTC 
Created attachment 861789 [details]
failed ovirt-engine installation

Description of problem:
Installing as a VM the iso with ovirt-3.4 resources, clicked automatic installation for ovirt-engine, the setup fails with the following output:

[ INFO  ] Starting engine service
[ INFO  ] Restarting httpd
 detail: Cannot add Cluster. CPU type must be specified
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140211072316.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed


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


How reproducible:
100%
Comment 1 Sandro Bonazzola 2014-02-13 14:09:37 UTC 
triggering error: detail: Cannot add Cluster. CPU type must be specified

2014-02-11 07:23:27 DEBUG otopi.plugins.**FILTERED**_engine_setup.**FILTERED**_engine.all-in-one.cpu cpu._getCompatibleCpuModels:75 Attempting to load the caps vdsm module
2014-02-11 07:23:27 DEBUG otopi.plugins.**FILTERED**_engine_setup.**FILTERED**_engine.all-in-one.cpu cpu._validation:126 Compatible CPU models are: []

2014-02-11 07:25:24 DEBUG otopi.context context.dumpEnvironment:471 ENV OVESETUP_AIO/supported=bool:'False'
2014-02-11 07:25:24 DEBUG otopi.context context.dumpEnvironment:471 ENV OVESETUP_AIO/vdsmCpu=NoneType:'None'


ovirt live plugin should not be enabled and abort the setup if OVESETUP_AIO/supported=bool:'False'
Comment 2 Ohad Basan 2014-02-20 11:44:14 UTC 
I will reopen as another bug.
which is not severe
in this case it failed because the AIO was running on a vm without nested virt.
besides the cluster is being created by AIO and not by ovirt-live
I am not hitting that problem on a regular hardware.