Automation Suite has pods which show logs manifesting a “Fatal glibc error: CPU does not support x86-64-v2”.
Description: This scenario is when certain apps in Automation Suite has pods which show logs manifesting a “Fatal glibc error: CPU does not support x86-64-v2”.
Identification and Troubleshooting: Such a scenario would theoretically be more likely to occur in an on-premise setup with hypervisors like VMware’s ESX or Microsoft’s HyperV.
The two pictures below show the outputs of less /proc/cpuinfo on the Linux terminal of an Automation Suite server before and after changes were made on the ESX host the server was hosted on. The main suspected difference is the absence of sse4_1 and sse4_2 flags in the first picture, which is the time where the error manifested. Upon being fixed at the hardware level (i.e. having sse4_1 and sse4_2 visible again), the error disappears.
Possible causes at the Hypervisor/ hardware level:
- vMotion or equivalent operation to a host that is running legacy CPU architecture
- VMware EVC being configured to use a lower-specification (try Ivy-Bridge or Haswell at minimum if these options are available to mitigate)
- Hypervisor settings potentially not allowing host-passthrough or having settings that restrict the server to certain CPU classes or generations.
- Problem resolution will be to rollback host-based changes to the settings prior to issue occurring, and/or adjusting hypervisor options to enable host-passthrough or a combination thereof.