Skip to content
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

panic: assignment to entry in nil map #2531

Closed
justinwalz opened this issue Apr 6, 2017 · 3 comments · Fixed by #2544
Closed

panic: assignment to entry in nil map #2531

justinwalz opened this issue Apr 6, 2017 · 3 comments · Fixed by #2544

Comments

@justinwalz
Copy link
Contributor

justinwalz commented Apr 6, 2017

This happened on two machines running nomad in server mode.

I know I'm running an older version, but submitting this bug in case it is still an issue in the latest release.

Nomad version

Output from nomad version
Nomad v0.5.2

Operating system and Environment details

Linux ip-10-201-0-8 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Issue

panic: assignment to entry in nil map

goroutine 11240414 [running]:
panic(0xfc0740, 0xc71652ac10)
        /opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hashicorp/nomad/nomad.evaluatePlan.func1(0xc70eec3aa0, 0x24, 0xc72274fb01, 0x0, 0x0, 0x1)
        /opt/gopath/src/github.com/hashicorp/nomad/nomad/plan_apply.go:252 +0x2c2
github.com/hashicorp/nomad/nomad.evaluatePlan(0xc763b18240, 0xc6b94ad260, 0xc701eba500, 0x0, 0x0, 0x0)
        /opt/gopath/src/github.com/hashicorp/nomad/nomad/plan_apply.go:276 +0xad4
github.com/hashicorp/nomad/nomad.(*Server).planApply(0xc4201fb1e0)
        /opt/gopath/src/github.com/hashicorp/nomad/nomad/plan_apply.go:82 +0x171
created by github.com/hashicorp/nomad/nomad.(*Server).establishLeadership
        /opt/gopath/src/github.com/hashicorp/nomad/nomad/leader.go:123 +0xde
    Loaded configuration from /etc/nomad/config.hcl

Reproduction steps

None

Nomad Server logs (if appropriate)

logfile.txt

@dadgar
Copy link
Contributor

dadgar commented Apr 6, 2017

@justinwalz Thanks for filing! That code hasn't changed so it is a valid issue

@dadgar
Copy link
Contributor

dadgar commented Apr 10, 2017

@justinwalz Do you have all_at_once set on any job file? https://www.nomadproject.io/docs/job-specification/job.html#all_at_once

dadgar added a commit that referenced this issue Apr 10, 2017
This PR fixes a potential source of a panic while evaluating a plan with
all_at_once set to true with partial failures.

Potentially fixes #2531
dadgar added a commit that referenced this issue Apr 10, 2017
This PR fixes a potential source of a panic while evaluating a plan with
all_at_once set to true with partial failures.

Fixes #2531
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants