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
debug port-forward does not work on 4.6 cluster #4036
Comments
I set the priority as high because its blocking 4.6 cluster to enable in periodic job against prow. |
@kadel I am hitting the same problem for devfile nodejs components. |
This is the output I get on 4.5.7 (from cluster-bot): oc -n openshift get is java -o yaml
and: oc -n openshift get is nodejs -o yaml
|
Running on CRC: $ oc version oc -n openshift get is java -o yaml
and: oc -n openshift get is nodejs -o yaml
|
Are the periodic jobs still failing on this? Or did things get fixed with #4016 getting closed?
Is this still a problem? Is it blocking VS Code plugin team? I'm asking this because I'm not seeing much activity on this issue and am inclined to lower its priority if it's not an annoyance to anyone. Plus, we're very low on bandwidth currently and need to focus on things that are absolute blockers/annoyance. |
/kind bug
What versions of software are you using?
Operating System:
All supported
Output of
odo version
:master
How did you run odo exactly?
Actual behavior
When I browse the
http://localhost:54753
, it throws connection refused. The same behaviour I have observed through the test script as well.Expected behavior
odo debug port-forward
should work.Any logs, error output, etc?
The text was updated successfully, but these errors were encountered: