start a debug session and run debug info on a closed debug session fails on 4.4 cluster

[amitkrout]

/kind bug

What versions of software are you using?

Operating System:
All supported
Output of odo version:
master

How did you run odo exactly?

Run make test-cmd-debug on 4.4 cluster.

Actual behavior

Test scenario should work

Expected behavior

Fails

Any logs, error output, etc?

 ------------------------------
Created dir: /tmp/711795762
Creating a new project: ukgyufpooc
Running odo with args [odo project create ukgyufpooc -w -v4]
[odo]  •  Waiting for project to come up  ...
[odo] I0226 10:11:07.485281   17082 occlient.go:538] Project ukgyufpooc now exists
[odo]  ✓  Waiting for project to come up [1s]
[odo]  ✓  Project 'ukgyufpooc' is ready for use
[odo]  ✓  New project created and now using project: ukgyufpooc
[odo] I0226 10:11:07.501801   17082 odo.go:80] Could not get the latest release information in time. Never mind, exiting gracefully :)
Running odo with args [odo component create nodejs:latest nodejs-cmp-ukgyufpooc --project ukgyufpooc --context /tmp/711795762]
[odo] Warning: nodejs:latest is not fully supported by odo, and it is not guaranteed to work
[odo]  •  Validating component  ...
[odo]  ✓  Validating component [59ms]
[odo] 
[odo] Please use `odo push` command to create the component with source deployed
Running odo with args [odo push --context /tmp/711795762]
[odo] Validation
[odo]  •  Checking component  ...
[odo]  ✓  Checking component [96ms]
[odo] 
[odo] Configuration changes
[odo]  ✓  Initializing component
[odo]  •  Creating component  ...
[odo]  ✓  Creating component [303ms]
[odo] 
[odo] Pushing to component nodejs-cmp-ukgyufpooc of type local
[odo]  •  Checking files for pushing  ...
[odo]  ✓  Checking files for pushing [659553ns]
[odo]  •  Waiting for component to start  ...
[odo]  ✓  Waiting for component to start [23s]
[odo]  •  Syncing files to the component  ...
[odo]  ✓  Syncing files to the component [411ms]
[odo]  •  Building component  ...
[odo]  ✓  Building component [10s]
[odo]  ✓  Changes successfully pushed to component
Checking http://localhost:34129, for WebSockets request was expected
try 0 of 12
Running odo with args [odo debug port-forward --local-port 34129 --context /tmp/711795762]
error while requesting: Get http://localhost:34129: dial tcp [::1]:34129: connect: connection refused
[odo] Started port forwarding at ports - 34129:5858
try 1 of 12
[odo] E0226 10:11:46.969078   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:11:46 socat[102267] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 2 of 12
[odo] E0226 10:11:52.038755   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:11:52 socat[102432] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 3 of 12
[odo] E0226 10:11:57.108054   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:11:57 socat[102814] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 4 of 12
[odo] E0226 10:12:02.174254   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:02 socat[103081] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 5 of 12
[odo] E0226 10:12:07.240362   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:07 socat[103222] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 6 of 12
[odo] E0226 10:12:12.308090   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:12 socat[103404] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 7 of 12
[odo] E0226 10:12:17.375382   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:17 socat[103539] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 8 of 12
[odo] E0226 10:12:22.442940   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:22 socat[103696] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 9 of 12
[odo] E0226 10:12:27.510025   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:27 socat[103832] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 10 of 12
[odo] E0226 10:12:32.576073   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:32 socat[104000] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
try 11 of 12
[odo] E0226 10:12:37.642093   17147 portforward.go:391] an error occurred forwarding 34129 -> 5858: error forwarding port 5858 to pod f5fc0458f264a579a07e9b08703478d45e20aa14a9bd9b0ad59c7207a2023837, uid : exit status 1: 2020/02/26 10:12:37 socat[104284] E connect(5, AF=2 127.0.0.1:5858, 16): Connection refused
error while requesting: Get http://localhost:34129: EOF
Last output from http://localhost:34129: 
Deleting project: ukgyufpooc
Running odo with args [odo project delete ukgyufpooc -f]
[odo] This project contains the following applications, which will be deleted
[odo] Application app
[odo] This application has following components that will be deleted
[odo] component named nodejs-cmp-ukgyufpooc
[odo] No services / could not get services
[odo]  •  Deleting project ukgyufpooc  ...
[odo]  ✓  Deleting project ukgyufpooc [6s]
[odo]  ✓  Deleted project : ukgyufpooc
Deleting dir: /tmp/711795762
• Failure [103.703 seconds]
odo debug command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_debug_test.go:16
  odo debug info should work on a odo component
  /go/src/github.com/openshift/odo/tests/integration/cmd_debug_test.go:71
    should start a debug session and run debug info on a closed debug session [It]
    /go/src/github.com/openshift/odo/tests/integration/cmd_debug_test.go:93
    Failed after 12 retries. Content in http://localhost:34129 doesn't include 'WebSockets request was expected'.
    /go/src/github.com/openshift/odo/tests/helper/helper_http.go:50
------------------------------ 

[kadel]

/area debug

[girishramnani]

this seems to be resolved via this PR #2729 @amitkrout . Can you please confirm?

[amitkrout]

@girishramnani I have test the your pr #2729 against 4.4 cluster for debug test and the above reported scenario went fine.