Host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
3:22 a.m.
Hi, can you help me please. After installing the node, the host gets the status of blah
blah, node and engine is installed on ec2 instances
5:22 a.m.
New subject: Host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
Here is cat /proc/cpuinfo | head -n 26 output
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 85
model name: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode: 0x2006906
cpu MHz : 2499.998
cache size: 33792 KB
physical id: 0
siblings: 8
core id: 0
cpu cores: 4
apicid: 0
initial apicid:0
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology
nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid
rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl
xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke bugs: cpu_meltdown
spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips: 4999.99
clflush size: 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
And engine.log file
2021-11-04 12:16:50,553Z INFO
[org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-61) [2cf2c819] Lock
freed to object
'EngineLock:{exclusiveLocks='[e8c52ac7-1da1-4626-b1d3-99e7ff73894f=PROVIDER]',
sharedLocks=''}'
2021-11-04 12:20:00,011Z INFO
[org.ovirt.engine.core.bll.AutoRecoveryManager]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [] Autorecovering
1 hosts 2021-11-04 12:20:00,011Z INFO
[org.ovirt.engine.core.bll.AutoRecoveryManager]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [] Autorecovering
hosts id: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b , name : ovirt.host_1
202
1-11-04 12:20:00,012Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
Acquired to object
'EngineLock:{exclusiveLocks='[356bd3e0-8bb6-4cd6-94b5-a155091b9a3b=VDS]',
sharedLocks=''}'
2021-11-04 12:20:00,017Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Running
command: ActivateVdsCommand internal: true. Entities affected : ID:
356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDSAction group MANIPULATE_HOST with role type
ADMIN 2021-11-04
12:20:00,017Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Before
acquiring lock in order to prevent m
onitoring for host 'ovirt.host_1' from data-center 'Default'
2021-11-04 12:20:00,017Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
acquired, from now a monitoring of host will be skipped for host 'ovirt.host_1'
from data-center 'Default'
2021-11-04
12:20:00,020Z INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] START,
SetVdsStatusVDSCommand(HostName = ovirt.host_1,
SetVdsStatusVDSCommandParameters:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
status='Unassigned', nonOperationalReason='NONE',
stopSpmFailureLogged='false', maintenanceReason=
'null'}), log id: 4e236062
2021-11-04 12:20:00,022Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] FINISH,
SetVdsStatusVDSCommand, return: , log id: 4e236062
2021-11-04 12:20:00,025Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b]
Activate host finished. Lock released. Monitoring can run now for host
'ovirt.host_1' from data-center 'Default'
2021-11-0
4 12:20:00,026Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
freed to object
'EngineLock:{exclusiveLocks='[356bd3e0-8bb6-4cd6-94b5-a155091b9a3b=VDS]',
sharedLocks=''}'
2021-11-04 12:20:03,393Z
INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [] START,
GetHardwareInfoAsyncVDSCommand(HostName = ovirt.host_1,
VdsIdAndVdsVDSCommandParametersBase:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
vds='Host[ovirt.host_1,356bd3e0-8bb6-4cd6-94b5-a155091b9a3b]'}), log id: 3153a576
2021-11-04
12:20:03,393Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [] FINISH,
GetHardwareInfoAsyncVDSCommand, return: , log id: 3153a576
2021-11-04 12:20:03,408Z INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [7f48d740]
Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,418Z INFO
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
Running command: SetNonOperationalVdsComm
and internal: true. Entities affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type:
VDS
2021-11-04 12:20:03,420Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4] START,
SetVdsStatusVDSCommand(HostName = ovirt.host_1,
SetVdsStatusVDSCommandParameters:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
status='NonOperational',
nonOperationalReason='CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 669e2b8a
2021-11-04 12:20:03,422Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
FINISH, SetVdsStatusVDSCommand, return: ,
log id: 669e2b8a
2021-11-04 12:20:03,429Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host ovirt.host_1 moved to
Non-Operational state as host CPU type is not supported in this cluster compatibility
version or is not supported at all 2021-11-04 12:20:03,434Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host ovirt.host_1 moved to
Non-Operational state as host CPU type is not supported in this cluster compatibility
version or is not supported at all 2021-11-04 12:20:
03,437Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: VDS_DETECTED(13), Status of host ovirt.host_1 was set to NonOperational.
2021-11-04 12:20:03,446Z INFO
[org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fdcda8] Running
command: HandleVdsVersionCommand internal: true. Entities affected : ID:
356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,450Z INFO
[org.ovirt.engine.core.bll.HandleVdsFipsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [4a73b1a0]
Running command: HandleVdsFipsCommand internal: true.
Entities affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,450Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [4a73b1a0] Host
'ovirt.host_1'(356bd3e0-8bb6-4cd6-94b5-a155091b9a3b) is already in NonOperational
status for reason 'CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION'.
SetNonOperationalVds command is skipped.
7:07 a.m.
New subject: Host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
Hi,
what's the ovirt version?
what's the cluster level you're trying to add/use?
EC2 bare metal instances?...even that might not really work, I don't know about ec2
specifically, but often these are not full bare metals and may not really work with kvm.
Thanks,
michal
On 4. 11. 2021, at 13:22, sekevgeniyig(a)gmail.com wrote:
Here is cat /proc/cpuinfo | head -n 26 output
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 85
model name: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode: 0x2006906
cpu MHz : 2499.998
cache size: 33792 KB
physical id: 0
siblings: 8
core id: 0
cpu cores: 4
apicid: 0
initial apicid:0
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush
mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology
nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid
rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl
xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke bugs: cpu_meltdown
spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips: 4999.99
clflush size: 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
And engine.log file
2021-11-04 12:16:50,553Z INFO
[org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-61) [2cf2c819] Lock
freed to object
'EngineLock:{exclusiveLocks='[e8c52ac7-1da1-4626-b1d3-99e7ff73894f=PROVIDER]',
sharedLocks=''}'
2021-11-04 12:20:00,011Z INFO
[org.ovirt.engine.core.bll.AutoRecoveryManager]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [] Autorecovering
1 hosts 2021-11-04 12:20:00,011Z INFO
[org.ovirt.engine.core.bll.AutoRecoveryManager]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [] Autorecovering
hosts id: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b , name : ovirt.host_1
202
1-11-04 12:20:00,012Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
Acquired to object
'EngineLock:{exclusiveLocks='[356bd3e0-8bb6-4cd6-94b5-a155091b9a3b=VDS]',
sharedLocks=''}'
2021-11-04 12:20:00,017Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Running
command: ActivateVdsCommand internal: true. Entities affected : ID:
356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDSAction group MANIPULATE_HOST with role type
ADMIN 2021-11-04
12:20:00,017Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Before
acquiring lock in order to prevent m
onitoring for host 'ovirt.host_1' from data-center 'Default'
2021-11-04 12:20:00,017Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
acquired, from now a monitoring of host will be skipped for host 'ovirt.host_1'
from data-center 'Default'
2021-11-04
12:20:00,020Z INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] START,
SetVdsStatusVDSCommand(HostName = ovirt.host_1,
SetVdsStatusVDSCommandParameters:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
status='Unassigned', nonOperationalReason='NONE',
stopSpmFailureLogged='false', maintenanceReason=
'null'}), log id: 4e236062
2021-11-04 12:20:00,022Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] FINISH,
SetVdsStatusVDSCommand, return: , log id: 4e236062
2021-11-04 12:20:00,025Z INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b]
Activate host finished. Lock released. Monitoring can run now for host
'ovirt.host_1' from data-center 'Default'
2021-11-0
4 12:20:00,026Z INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [2a4de00b] Lock
freed to object
'EngineLock:{exclusiveLocks='[356bd3e0-8bb6-4cd6-94b5-a155091b9a3b=VDS]',
sharedLocks=''}'
2021-11-04 12:20:03,393Z
INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [] START,
GetHardwareInfoAsyncVDSCommand(HostName = ovirt.host_1,
VdsIdAndVdsVDSCommandParametersBase:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
vds='Host[ovirt.host_1,356bd3e0-8bb6-4cd6-94b5-a155091b9a3b]'}), log id: 3153a576
2021-11-04
12:20:03,393Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [] FINISH,
GetHardwareInfoAsyncVDSCommand, return: , log id: 3153a576
2021-11-04 12:20:03,408Z INFO
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [7f48d740]
Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities
affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,418Z INFO
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
Running command: SetNonOperationalVdsComm
and internal: true. Entities affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type:
VDS
2021-11-04 12:20:03,420Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4] START,
SetVdsStatusVDSCommand(HostName = ovirt.host_1,
SetVdsStatusVDSCommandParameters:{hostId='356bd3e0-8bb6-4cd6-94b5-a155091b9a3b',
status='NonOperational',
nonOperationalReason='CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 669e2b8a
2021-11-04 12:20:03,422Z INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
FINISH, SetVdsStatusVDSCommand, return: ,
log id: 669e2b8a
2021-11-04 12:20:03,429Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host ovirt.host_1 moved to
Non-Operational state as host CPU type is not supported in this cluster compatibility
version or is not supported at all 2021-11-04 12:20:03,434Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host ovirt.host_1 moved to
Non-Operational state as host CPU type is not supported in this cluster compatibility
version or is not supported at all 2021-11-04 12:20:
03,437Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fd74af4]
EVENT_ID: VDS_DETECTED(13), Status of host ovirt.host_1 was set to NonOperational.
2021-11-04 12:20:03,446Z INFO
[org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [6fdcda8] Running
command: HandleVdsVersionCommand internal: true. Entities affected : ID:
356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,450Z INFO
[org.ovirt.engine.core.bll.HandleVdsFipsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [4a73b1a0]
Running command: HandleVdsFipsCommand internal: true.
Entities affected : ID: 356bd3e0-8bb6-4cd6-94b5-a155091b9a3b Type: VDS
2021-11-04 12:20:03,450Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-13) [4a73b1a0] Host
'ovirt.host_1'(356bd3e0-8bb6-4cd6-94b5-a155091b9a3b) is already in NonOperational
status for reason 'CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION'.
SetNonOperationalVds command is skipped.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MT3SSJ2MOR7...
7:13 a.m.
New subject: Host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all
Thanks for reply,
Ovirt version 4.4
Not sure about cluster level, this is my first time with ovirt i just follow this
instructions
https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_mana...
AWS Instance type t3.2xlarge
904
days inactive
904
days old
3 comments
2 participants
participants (2)
-
Michal Skrivanek -
sekevgeniyig＠gmail.com