Bug 1519732 - Invalid cpu familly name in answer file
Summary: Invalid cpu familly name in answer file
Keywords:
Status: CLOSED DUPLICATE of bug 1516113
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: ---
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ryan Barry
QA Contact: Yihui Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-01 10:45 UTC by Bernhard Seidl
Modified: 2017-12-07 02:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-07 02:45:35 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2?
cshao: testing_ack?

Attachments (Terms of Use)
CPU model error (48.21 KB, image/png)
2017-12-01 10:45 UTC, Bernhard Seidl 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84766 0 None None None 2017-12-06 11:18:47 UTC

Description Bernhard Seidl 2017-12-01 10:45:07 UTC 
Created attachment 1361504 [details]
CPU model error

Description of problem:
The configuration script just adds the cpu famiily name to the answer script:
OVEHOSTED_VDSM/cpu=str:Broadwell

However ovirt-hosted-engine-setup seems to expect a "model_" prefix to that:
OVEHOSTED_VDSM/cpu=str:model_Broadwell

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


How reproducible:
Installing a hosted engine

Steps to Reproduce:
1. Start engine installation

Actual results:
OVEHOSTED_VDSM/cpu=str:Broadwell in answer file

Expected results:
OVEHOSTED_VDSM/cpu=str:model_Broadwell

Additional info:
Comment 1 Bernhard Seidl 2017-12-06 10:07:16 UTC 
Seems to work in
ovirt-node-ng-installer-master-2017120509.iso
ovirt-engine-appliance-4.2-20171205.1.el7.centos.noarch.rpm
Comment 2 Yihui Zhao 2017-12-07 02:45:35 UTC 
The same issue as the bug 1516113.

*** This bug has been marked as a duplicate of bug 1516113 ***

*** This bug has been marked as a duplicate of bug 1516113 ***
Note You need to log in before you can comment on or make changes to this bug.