You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Latest nomad master
Operating system and Environment details
Issue
On some arm64 Ec2 instances, Nomad fails to properly fingerprint cpu, even though they are specified in our AWS EC2 lookup table.
Consider
t4g.large
instance, it's specified innomad/client/fingerprint/env_aws_cpu.go
Line 386 in cf6055e
/cpu/cpuinfo
doesn't contain acpu MHz
line, the basic detector fails anyway due to the check innomad/client/fingerprint/cpu.go
Lines 61 to 73 in cf6055e
Reproduction steps
Start nomad 1.0.0-beta3 on a t4.large:
nomad agent -dev
Observe:
The text was updated successfully, but these errors were encountered: