-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
DiskMB property of the HTTP API Job Spec is not having any effect on disk requirement #2401
Comments
dadgar
added a commit
that referenced
this issue
Mar 6, 2017
@ncodes Thanks for catching that! Will be fixed in 0.5.5 |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Nomad version
Nomad v0.5.4
Operating system and Environment details
Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-64-generic x86_64)
Issue
I am currently creating jobs through the HTTP API and I noticed that the disk resource is always set to 0 in the Task Resource section of
nomad alloc-status ...
. Runningnomad inspect ...
on the job showsEphemeralDisk.SizeMB
of task group still set to the default300
even whenDiskMB
of the job spec is set to a different value. I looked at the source and foundTaskGroups.EphemeralDisk
, applied it, rannomad alloc-status ...
and got the expected value. But the output ofnomad alloc-status ...
still showedDisk
to be 0.Reproduction
curl -X POST http://localhost:4646/v1/jobs -d '{ ... }'
Nomad Client logs (if appropriate)
Job file (if appropriate)
This is the initial job spec without the
EphemeralDisk
task group property.This one includes the
EphemeralDisk
propertyThe text was updated successfully, but these errors were encountered: