-
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
fix nil pointer exception when running status with failed allocations #2604
Conversation
@clinta What version of Nomad are you on? There shouldn't ever be an allocation without a job so it is really a bug that this would be masking. |
I'm running from master, because I need the feature in #2535 which has not yet made it into a release. Here's some logs that provide context of the allocation that got into this state. It was for the task group hdfs-namenode2. This container wouldn't start due to an issue with a docker volume driver. It appears that after it failed to start, nomad did not remove the container and tried to create it again, the subsequent create operations failing because the old container already existed.
|
@clinta And you were running in dev mode? I am going to close the PR and open an issue. |
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
When a job has an allocation which failed to be created alloc.Job is nil, causing a nil pointer exception and an empty file to be returned to
nomad status
.