Bug 1524132 - Failed to execute stage 'Environment customization': Invalid CPU type specified: IvyBridge
Summary: Failed to execute stage 'Environment customization': Invalid CPU type specifi...
Keywords:
Status: CLOSED DUPLICATE of bug 1516113
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Doron Fediuck
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-10 10:11 UTC by Nikolai Sednev
Modified: 2017-12-11 09:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-11 09:58:29 UTC
oVirt Team: Integration
Embargoed:
nsednev: planning_ack?
nsednev: devel_ack?
nsednev: testing_ack?


Attachments (Terms of Use)
sosreport from host (9.35 MB, application/x-xz)
2017-12-10 10:11 UTC, Nikolai Sednev
no flags Details
Screenshot from 2017-12-10 12-11-26.png (72.64 KB, image/png)
2017-12-10 10:12 UTC, Nikolai Sednev
no flags Details

Description Nikolai Sednev 2017-12-10 10:11:37 UTC
Created attachment 1365553 [details]
sosreport from host

Description of problem:
I've got this failure during deployment of SHE on latest NGN (RHEVH) Linux version 3.10.0-693.5.2.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Fri Oct 13 10:46:25 EDT 2017:

"Failed to execute stage 'Environment customization': Invalid CPU type specified: IvyBridge".

I think that CPU not properly recognized during deployment.

I'm using this CPU:

#  lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 62
Model name:            Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz
Stepping:              4
CPU MHz:               1800.000
CPU max MHz:           1800.0000
CPU min MHz:           1200.0000
BogoMIPS:              3599.99
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              10240K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm arat pln pts


Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-16.el7_4.8.x86_64
ovirt-release-master-4.2.0-0.6.master.20171210000025.git413064d.el7.centos.noarch
ovirt-hosted-engine-ha-2.2.0-0.2.master.gitcbe3c76.el7ev.noarch
ovirt-hosted-engine-setup-2.2.0-0.4.master.git0b67c21.el7ev.noarch
vdsm-4.20.8-1.el7ev.x86_64
rhvm-appliance-4.2-20171207.0.el7.noarch 


How reproducible:
100%

Steps to Reproduce:
1.Deploy SHE on NGN 4.2 over NFS.

Actual results:
Deployment fails with improperly recognized CPU family.

Expected results:
Deployment should succeed.

Additional info:
Sosreport from host is attached.

Comment 1 Nikolai Sednev 2017-12-10 10:12:37 UTC
Created attachment 1365554 [details]
Screenshot from 2017-12-10 12-11-26.png

Comment 2 Nikolai Sednev 2017-12-10 10:14:20 UTC
NGN was using cockpit:
cockpit-151-1.el7.x86_64
cockpit-ovirt-dashboard-0.11.1-0.4.el7ev.noarch

Comment 3 Nikolai Sednev 2017-12-11 09:58:29 UTC
Seems like this is a duplicate bug of https://bugzilla.redhat.com/show_bug.cgi?id=1516113.
Closing this bug as duplicate.

*** 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.