-
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
erroneous "cpu exhausted" message using qemu #302
Comments
Rolling this to nomad 0.1.2 fixes docker, partially fixes qemu. Qemu is now stating "failed to start: Missing source image Qemu driver" however this appears to be a check on the source address of the qemu image in qemu.go (https://github.com/hashicorp/nomad/blob/7ab84c2862d8f8de75e9ac64ee71b8a0cd05c798/client/driver/qemu.go) which is correct for my environment.
|
I suspect the original issue is possibly something in a dependent library changed since 0.1.2 was released (most likely shirou/gopsutil). If I check out v0.1.2 and rebuild locally it I get the same error about exhausted cpus. |
Yeah it looks like the current master tag of gopsutil is broken, get a nil object when testing the library, opened a bug report with the maintainer. Would not be a terrible idea to implement godep in the future to prevent these kinds of issues. |
The fix to gopsutil has been merged. You should be able to manually pull those changes and rebuild nomad. But yes, a way to reproduce build deterministically is absolutely essential. |
@rvm2015 Thanks for the detailed report. I think you're correct we will need |
Closing as this was from an upstream bug. |
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. |
Using current master, any qemu or docker instance I attempt to schedule is coming up unable to find a node for placement. This may or may not be because I'm attempting to run something paravirtualized (or I could just not have the nomad file built properly), if so it would be helpful if the allocator told me this. Tested with a 4 core node with 4 gigs of memory. I've run docker images on this setup with no issue before however they are also now failing. Command output:
example.nomad
The text was updated successfully, but these errors were encountered: