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

Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) #18474

Closed
16 tasks
gnoejuan opened this issue Nov 26, 2020 · 4 comments
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone

Comments

@gnoejuan
Copy link

Describe the bug

I'm unfortunately unable to figure out anything beyond the logs.

Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)

Error.txt and logs: https://1drv.ms/u/s!AoSeaeVYrPG8jL1mt-k_otuRka37-A?e=9TkESQ

Che version

  • [ x ] latest
  • nightly
  • other: please specify

Steps to reproduce

chectl server:deploy --che-operator-cr-yaml='/media/charlesrod/KINGSTON/kubernetes/k8s/che/che-cluster.yaml' -a operator -p k8s -b che-che.url.com

image

I've been able to deploy other k8s apps. Any further information I can give, just let me know.

Expected behavior

Runtime

  • [ x ] kubernetes (include output of kubectl version)
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"clean", BuildDate:"2020-11-16T17:18:52Z", GoVersion:"go1.15.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.9+k3s1", GitCommit:"630bebf94b9dce6b8cd3d402644ed023b3af8f90", GitTreeState:"clean", BuildDate:"2020-09-17T19:05:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • [ x ] other: (please specify): k3os

Screenshots

Installation method

  • [ x ] chectl
    • provide a full command that was used to deploy Eclipse Che (including the output)
    • provide an output of chectl version command
  • OperatorHub
  • I don't know

Environment

  • my computer
    • Windows
    • [ x ] Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • [ x ] other (please specify): k3os
  • other: please specify

Eclipse Che Logs

Additional context

@gnoejuan gnoejuan added the kind/bug Outline of a bug - must adhere to the bug report template. label Nov 26, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 26, 2020
@tolusha
Copy link
Contributor

tolusha commented Nov 27, 2020

Probably that is a location of the error:
https://github.com/eclipse/che-operator/blob/master/pkg/deploy/server/che_configmap.go#L285

@gnoejuan
Do you have che-tls secret created in a namespace ?

@amisevsk amisevsk added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 28, 2020
@gnoejuan
Copy link
Author

Do you have che-tls secret created in a namespace ?

This lead me to the correct solution. There was a problem with the tls secret outside of Che's scope. Thank you!

@tolusha
Copy link
Contributor

tolusha commented Dec 1, 2020

I will keep this issue opened for a while since NPE is not good anyway.

@tolusha tolusha reopened this Dec 1, 2020
@tolusha tolusha added severity/P2 Has a minor but important impact to the usage or development of the system. and removed severity/P1 Has a major impact to usage or development of the system. labels Dec 1, 2020
@tolusha tolusha added this to the 7.25 milestone Dec 16, 2020
@mmorhun mmorhun self-assigned this Dec 17, 2020
@mmorhun
Copy link
Contributor

mmorhun commented Dec 18, 2020

Fixed

@mmorhun mmorhun closed this as completed Dec 18, 2020
@tolusha tolusha modified the milestones: 7.25, 7.24 Dec 18, 2020
@tolusha tolusha mentioned this issue Dec 18, 2020
56 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants