
1 May
2024
1 May
'24
8:15 p.m.
I was able to determine the OVN issue is a current bug in 4.5.6 when using the FQDN for a new host. If I use the IP Address of the new ARM64 host it gets all the way to adding it and shows the below error and has a red X in the status of the host. Host oVirtNode3 moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all. The host does show memory, cpu, and network usage percentage on the hosts page, which says it can connect, it just doesn't have the config in the cluster creation to determine the architecture. Any help would be appreciated.