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

sentry: panic from makeMounts #13263

Closed
smarterclayton opened this issue Mar 6, 2017 · 5 comments
Closed

sentry: panic from makeMounts #13263

smarterclayton opened this issue Mar 6, 2017 · 5 comments

Comments

@smarterclayton
Copy link
Contributor

Form dev preview

runtime.errorString: runtime error: invalid memory address or nil pointer dereference
github.com/openshift/origin/pkg/cmd/util/serviceability.(*SentryMonitor) in CapturePanic-fm
MESSAGE

runtime error: invalid memory address or nil pointer dereference
EXCEPTION(most recent call first)FullRaw
runtime.errorString: runtime error: invalid memory address or nil pointer dereference
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/pkg/cmd/util/serviceability/panic.go", line 28, in CapturePanic-fm
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/util/runtime/runtime.go", line 49, in HandleCrash
  File "/usr/lib/golang/src/runtime/asm_amd64.s", line 479, in call32
  File "/usr/lib/golang/src/runtime/panic.go", line 458, in gopanic
  File "/usr/lib/golang/src/runtime/panic.go", line 62, in panicmem
  File "/usr/lib/golang/src/runtime/sigpanic_unix.go", line 24, in sigpanic
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go", line 1225, in makeMounts
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go", line 1388, in GenerateRunContainerOptions
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/dockertools/docker_manager.go", line 1666, in runContainerInPod
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/dockertools/docker_manager.go", line 2294, in tryContainerStart
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/dockertools/docker_manager.go", line 2263, in SyncPod
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go", line 1825, in syncPod
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go", line 694, in syncPod)-fm
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/pod_workers.go", line 172, in func1
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/pod_workers.go", line 178, in managePodLoop
  File "/builddir/build/BUILD/atomic-openshift-git-0.46178be/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/kubelet/pod_workers.go", line 216, in func1
  File "/usr/lib/golang/src/runtime/asm_amd64.s", line 2086, in goexit
@jingxu97
Copy link

jingxu97 commented Mar 6, 2017

@smarterclayton do you have more details about this issue? What type of volume is used?

@smarterclayton
Copy link
Contributor Author

smarterclayton commented Mar 6, 2017 via email

@jingxu97
Copy link

jingxu97 commented Mar 7, 2017

which version of k8s the cluster is using?

@smarterclayton
Copy link
Contributor Author

1.4.2 (ish).

@smarterclayton
Copy link
Contributor Author

@sjenning @derekwaynecarr since you guys have fixed the other one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants