-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fingerprinting OVH nodes with incorrect CPU frequency after upgrading to 1.7.1 #19406
Comments
Same issue on KVM VM + Docker, Nomad 1.7.1 as workaround you can override it.. my 2*3300MHz (eg from cat /proc/cpuinfo) = 6600Mhz client { restart nomad |
Potentially related: #19412 |
Somewhat related - after upgrading my raspberry pi cluster to use Nomad 1.7.1 I was seeing errors from the CPU fingerprinter.
I was able to fix this by creating the directory Nomad is looking for and it resolved the issue. It also happened in the pre_run hook as well:
|
@lindleydev that's actually a separate problem - I suspect in your case cgroups is mounted but the cpuset controller is not enabled. In previous versions of Nomad we allowed such a configuration at the expense of not actually enforcing resource utilization, but in 1.7 it's mandatory. There's some discussion about this happening in #19176 |
Possible reason of this issue described here: #19412 (comment) |
Hey folks, just an update that the team is actively working on this issue. This issue and #19412 are effectively duplicates, so I'm going to close this issue as a dupe because there's been a bit more discussion over there. |
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. |
Nomad version
Operating system and Environment details
ovh VPS with the following configuration:
Issue
After upgrading to 1.7.1, the OVH nodes in my nomad cluster report 0 MHZ fingerprinted CPU; however, if you look at the logs below you see that it detects 8 CPUs just not the clock speed for them.

I have another node in hetzner that it is able to properly detect the CPU frequency for. Downgrading to nomad 1.6.4 and restarting resolves then problem.
Reproduction steps
Start nomad client on a OVH node and have it join the cluster
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: