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.

Sign up for GitHub

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

Jump to bottom

"nil pointer dereference" error in scheduler while trying to schedule pod with cpu specified #5503

Closed
piosz opened this issue Mar 16, 2015 · 1 comment · Fixed by #5544
Closed

"nil pointer dereference" error in scheduler while trying to schedule pod with cpu specified #5503

piosz opened this issue Mar 16, 2015 · 1 comment · Fixed by #5544
Assignees
@piosz
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.0

Comments

@piosz
Copy link
Member

piosz commented Mar 16, 2015

When I'm trying to run pod with cpu specified (redis-master from guestbook example) I can see:

$ kubectl get pod redis-master-controller-v5drx
POD                             IP                  CONTAINER(S)        IMAGE(S)            HOST                LABELS                        STATUS              CREATED
redis-master-controller-v5drx                       redis-master        dockerfile/redis    <unassigned>        app=redis,name=redis-master   Pending             27 seconds

And in scheduler logs:

I0316 13:18:12.964614    4218 factory.go:156] About to try and schedule pod redis-master-controller-v5drx
I0316 13:18:12.964929    4218 util.go:68] Recovered from panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:62
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:53
/usr/src/go/src/runtime/asm_amd64.s:401
/usr/src/go/src/runtime/panic.go:387
/usr/src/go/src/runtime/panic.go:42
/usr/src/go/src/runtime/sigpanic_unix.go:26
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/scheduler/predicates.go:112
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/scheduler/predicates.go:138
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/scheduler/generic_scheduler.go:110
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/scheduler/generic_scheduler.go:63
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler/scheduler.go:75
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler/scheduler.go:69
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:107
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:108
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:92

The problem disappear when I remove line "cpu": 100, from pod specification.
@piosz piosz self-assigned this Mar 16, 2015
@piosz piosz added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. team/master labels Mar 16, 2015
piosz added a commit to piosz/kubernetes that referenced this issue Mar 16, 2015
@piosz
Removed resource specification from guestbook example
e6031e3 
The reason is partially kubernetes#5503 but also I think it makes guestbook more
complicated and is not necessary there.
@piosz piosz mentioned this issue Mar 16, 2015
Merged
@wojtek-t wojtek-t mentioned this issue Mar 16, 2015
Merged
@piosz
Copy link
Member Author

piosz commented Mar 16, 2015

Unassigning myself since I haven't done it today. Maybe someone from US timezone want to take a look?

If not I'm happy to back to it tomorrow.

@piosz piosz removed their assignment Mar 16, 2015
@piosz piosz self-assigned this Mar 17, 2015
@wojtek-t wojtek-t added this to the v1.0 milestone Mar 17, 2015
piosz added a commit to piosz/kubernetes that referenced this issue Mar 17, 2015
@piosz
Fill NodeInfo in CreateFromKey method in scheduler
7aa6356 
NodeInfo was nil and it caused segfault

Fixes kubernetes#5503
@piosz piosz mentioned this issue Mar 17, 2015
Merged
piosz added a commit that referenced this issue Mar 17, 2015
@piosz @zmerlynn
Fill NodeInfo in CreateFromKey method in scheduler
d5dc653 
NodeInfo was nil and it caused segfault

Fixes #5503
@piosz piosz mentioned this issue Mar 18, 2015
Closed
akram pushed a commit to akram/kubernetes that referenced this issue Apr 7, 2015
@piosz @akram
Removed resource specification from guestbook example
c42cdf9 
The reason is partially kubernetes#5503 but also I think it makes guestbook more
complicated and is not necessary there.
akram pushed a commit to akram/kubernetes that referenced this issue Apr 7, 2015
@piosz @akram
Fill NodeInfo in CreateFromKey method in scheduler
a6547a5 
NodeInfo was nil and it caused segfault

Fixes kubernetes#5503
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@piosz piosz

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.0
Development

Successfully merging a pull request may close this issue.

Fill NodeInfo in CreateFromKey method in scheduler piosz/kubernetes
2 participants
@wojtek-t @piosz