Component Debug command on Windows never results in starting debug session

[sjagadale]

Windows 10 Enterprise - 21H1
Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz 2.30 GHz
Power Cluster Openshift version - OCP 4.6
Z cluster Openshift version - OCP 4.8
OpenShift Connector v0.2.9

Steps to reproduce this issue,

1. Connect to OCP cluster
2. Create project
3. Create local directory and clone - git clone https://github.com/odo-devfiles/nodejs-ex use this to add in component add
4. Create component and above cloned directory
5. Push component to cluster - let the push be successfully complete.
6. Right click on component and start debug - at this stage you will see that debugging goes in hanging mode and dont return back.

PFA - screen shot of vscode debug.

[dgolovin]

@sjagadale Is there a chance it is a firewall or proxy issue?
Would you also try to run Describe command from the same menu. It is just to know full path to odo cli.
Then modify it to run
"path/to/odo" debug port-forward
what is an output?

[dgolovin]

I see I already have answer about odo debug port-forward

"c:\Users\KandarpaMalipeddi\.vscode\extensions\redhat.vscode-openshift-connector-0.2.7\out\tools\win32\odo.exe" debug port-forward
Started port forwarding at ports - 5858:5858
E0617 20:08:25.329125   23660 portforward.go:233] lost connection to pod

[xkwangcn]

@dgolovin Hello, I am the developer on Z cluster, I have a question, did you test the debug feature from windows to x86? Could it success use debug on your windows machine? Thank you.

[dgolovin]

@xkwangcn It was working fine when I have tested it before latest release. I'll test it again because I just found out it does not work at all after VSCode update to v1.60.0 (see #2233 fro details)
CC: @mohitsuman

[dgolovin]

@xkwangcn do you still see lost connection to pod when you run `odo debug port-forward' command above?
Could you run it again with additional option '-v 10', just to see if odo reports any additional information.

[xkwangcn]

@dgolovin Thanks. I don't have windows machine and not see lost connection to pod when use @sjagadale 's machine test.
Hello @sjagadale , could you help to run #2229 (comment) again and give the result here? Thank you.

[xkwangcn]

@sjagadale what about your VSCode's version?

[xkwangcn]

@xkwangcn It was working fine when I have tested it before latest release. I'll test it again because I just found out it does not work at all after VSCode update to v1.60.0 (see #2233 fro details)
CC: @mohitsuman

OK. maybe this related to VSCode version? My VSCode is Version: 1.59.0 (Universal) and working fine for Z and P.
@sjagadale and I will also check it for new version. Thank you.

[sjagadale]

@xkwangcn @mohitsuman My VS code version 1.61.0 and Openshift connector version 0.2.9
Any update on this please.

[dgolovin]

@sjagadale Debug would not work for nodejs in 1.61.0. I'll issue update to fix it. One's it is out please let me know if you still experience the issue.

[sjagadale]

@dgolovin
I have verified on latest version 1.61.1 - issue persist.
if you have not updated fix.
Please let us know when fix is ready.

[dgolovin]

@sjagadale I have replicated the issue on windows with remote cluster. Working on fixing it and releasing update. Thanks!

[kandarpamalipeddi]

Verified on v0.2.13, Debug feature is working fine on Power cluster.