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

Go Panic when running odo dev with minikube #7140

Open
AgentK9 opened this issue Oct 31, 2023 · 4 comments
Open

Go Panic when running odo dev with minikube #7140

AgentK9 opened this issue Oct 31, 2023 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@AgentK9
Copy link

AgentK9 commented Oct 31, 2023

/kind bug

What versions of software are you using?

Operating System:

Ubuntu

Output of odo version:

3.15.0

How did you run odo exactly?

sudo odo dev --logs --port-forward 8000:8000

Actual behavior

Errored on run with a go panic.

Expected behavior

A. Run odo dev as normal (this command and devfile work fine in windows/mac environments with docker desktop). The main differences with this dev's environment is that odo is being run on ubuntu with minikube as the k8s backend, instead of docker-desktop's k8s cluster.
B. The error (Failed to delete inner loop resources: failed to get deployment "<project-name>-app": Get "https://192.168.49.2:8443/apis/apps/v1/namespaces/default/deployments/<project-name>-app": Forbidden) seems like it could be an issue with the minikube configuration, which is understandable. However, in this case, odo should not panic and instead print out a helpful error message.

Any logs, error output, etc?

Error output:

  __
 /  \__     Developing using the "<project-name>" Devfile
 \__/  \    Namespace: default
 /  \__/    odo version: v3.15.0 (10b5e8a8f)
 \__/

==================================================================================================================================
⚠  You are using "default" namespace, odo may not work as expected in the default namespace.
You may set a new namespace by running `odo create namespace <name>`, or set an existing one by running `odo set namespace <name>`
==================================================================================================================================

↪ Running on the cluster in Dev mode
 ✓  Web console accessible at http://localhost:20000/ 
 ✓  API Server started at http://localhost:20000/api/v1 
 ✓  API documentation accessible at http://localhost:20000/swagger-ui/ 
Cleaning resources, please wait
Failed to delete inner loop resources: failed to get deployment "<project-name>-app": Get "https://192.168.49.2:8443/apis/apps/v1/namespaces/default/deployments/<project-name>-app": Forbidden
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x2da3040]

goroutine 31 [running]:
github.com/redhat-developer/odo/pkg/logs.(*LogsClient).getLogsForMode(0xc00049f7e0, {0x481d518, 0xc000a54720}, {0xc000062c00?, 0xc000062c60?, 0xc000062cc0?}, {0x35407d4, 0x3}, {0xc000a52400, 0x8}, ...)
    /builddir/build/BUILD/gocode/src/github.com/redhat-developer/odo/pkg/logs/logs.go:282 +0x360
created by github.com/redhat-developer/odo/pkg/logs.(*LogsClient).GetLogsForMode
    /builddir/build/BUILD/gocode/src/github.com/redhat-developer/odo/pkg/logs/logs.go:208 +0x1d2
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 31, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 31, 2023
@AgentK9 AgentK9 changed the title Go Panic when running Go Panic when running odo dev with minikube Oct 31, 2023
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@AgentK9
Copy link
Author

AgentK9 commented Feb 1, 2024

Still an issue!

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2024
Copy link
Contributor

github-actions bot commented May 2, 2024

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 2, 2024
@AgentK9
Copy link
Author

AgentK9 commented May 2, 2024

Still an issue...

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
Status: No status
Development

No branches or pull requests

1 participant