Cloud Code IntelliJ Stuck

ericbrown30 commented 1 year ago

(Please ensure you are running the latest version of Cloud Cloud IntelliJ with Help > Check for Updates.)

(screenshots are often helpful)

Expected Behavior

When running Develop on Kuberenetes for hello-world-java application. It should be deployed on local minikube and debug session should be started.

Actual Behavior

Logs stuck on

Validating Kubernetes dependencies...
Validating Docker settings...
Validating image repository settings...

Status of minikube api-server is RUNNING

issue

Additional Information

IDE type: IntelliJ
IDE version: Ultimate 2022.2
Cloud Code version (Settings > Plugins > Cloud Code): 22.11.1-222
Cloud SDK (Settings > Cloud Code > Cloud SDK)
- Are you allowing the plugin to manage the Cloud SDK: Yes
- Version of the Cloud SDK: 410.0.0
Skaffold version (If you are using Kubernetes features; Settings > Cloud Code > Kubernetes): 2.0.1
Operating System: Debian Running in WSL2 Windows 10

etanshaul commented 1 year ago

hi @asaqib27 , did you select the following option in the Run Config?

Regardless, it looks like minikube is stuck for whatever reason. Can you try stopping minikube manually? (if you are using Cloud Code's managed minikube (the option in the screenshot above) you can access minikube from the command line by selecting Tools > Cloud Code > Tools > Cloud Code Terminal

minikube stop if that doesn't help minikube delete to delete the cluster and, lastly minikube delete --purge --all warning: this will purge everything from ALL minikube profiles, so only use if you are certain.

ericbrown30 commented 1 year ago

I am able to run everything in Win10 successfully. I am only facing this problem in WSL2. I tried unfortunately, it didn't work but I got few logs.

Validating Kubernetes dependencies...
Validating Docker settings...
Validating image repository settings...

Status of minikube api-server is UNDEFINED

minikube may take several minutes to start up...

Starting minikube

/home/abra0822/.cache/google-cloud-tools-java/managed-cloud-sdk/LATEST/google-cloud-sdk/bin/minikube start --wait true --vm-driver docker --interactive false --delete-on-failure --user cloud-code-intellij
* minikube v1.28.0 on Debian 11.3
  - MINIKUBE_WANTUPDATENOTIFICATION=false
* Using the docker driver based on user configuration
* Using Docker driver with root privileges
* Starting control plane node minikube in cluster minikube
* Pulling base image ...
* Downloading Kubernetes v1.25.3 preload ...
* Creating docker container (CPUs=2, Memory=3700MB) ...
* Preparing Kubernetes v1.25.3 on Docker 20.10.20 ...
  - Generating certificates and keys ...
  - Booting up control plane ...
  - Configuring RBAC rules ...
* Verifying Kubernetes components...
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: default-storageclass, storage-provisioner
E1201 03:07:02.926304   14764 pod_ready.go:66] WaitExtra: waitPodCondition: error getting pod "coredns-565d847f94-qh7tg" in "kube-system" namespace (skipping!): pods "coredns-565d847f94-qh7tg" not found

! /home/abra0822/.cache/cloud-code/bin/versions/1357d1cbe7ce9e7778f335b6a0fa97547e5e412453383a71032ddcf1bb63e815/kubectl is version 1.21.0, which may have incompatibilities with Kubernetes 1.25.3.
  - Want kubectl v1.25.3? Try 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

minikube started successfully.

Can this error cause any problem?

E1201 03:07:02.926304   14764 pod_ready.go:66] WaitExtra: waitPodCondition: error getting pod "coredns-565d847f94-qh7tg" 
in "kube-system" namespace (skipping!): pods "coredns-565d847f94-qh7tg" not found

etanshaul commented 1 year ago

It is interesting that minikube started up successfully - did it just freeze at this point (no output afterwards)?

Regarnding that error you refer to, I don't think that should cause things to completely stall out. If anything, the deployment should proceed and then cause issues downstream (I am not sure though if it would).

ericbrown30 commented 1 year ago

@etanshaul Yes, it just freezes at this point. I even left it for 20 minutes just to check if anything will happen. Unfortunately, nothing happened (I haven't received any logs, this process hasn't terminated automatically & throws an error). It just stuck at this point without any other logs.

ericbrown30 commented 1 year ago

It is worth mentioning that same setup is working in vscode + cloud code. Don't understand how??

etanshaul commented 1 year ago

@asaqib27 a couple more thing to maybe get at the bottom of this (it might be a WSL issue):

1) can you turn on verbose logging for the Kubernetes session: edit the Run Configuration. Then under "Advanced Settings", there is an option to set the logging verbosity level to "DEBUG". Then run the session again. Maybe there is interesting output in the log.

2) Let's check if you can execute skaffold itself from the CLI (what Cloud Code uses to drive its Kubernetes deployments):

Goto Tools > Cloud Code > Tools > Cloud Code Terminal
Here you can interact with Cloud Code's managed Skaffold. Can you run skaffold version. Try running skaffold dev.

ericbrown30 commented 1 year ago

@etanshaul I tried it,

No further logs printed event in DEBUG mode.
I am able to execute skaffold via the cloud code terminal and it also deployed all the resources successfully.

etanshaul commented 1 year ago

hi @asaqib27 . the next step here is to try and fetch IDE logs around the time you perform the deployment. You can normally find them under Help -> Show Logs in Finder (for MacOs). Sharing a dump of these logs (redacting sensitive info) or a snippet that looks relevant, could help us debug.

ivanporty commented 1 year ago

Closing issue due to inactivity. Please reopen if this still happens for you in the latest version.

GoogleCloudPlatform / cloud-code-intellij