-
Notifications
You must be signed in to change notification settings - Fork 61
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
Login to cluster does not work #2693
Comments
@lgrossma could you try if |
This works for me as it uses oc version 4.9.5 which souldn't be affected by the error.
could you please provide me with macos executable? |
@lgrossma The extension uses this version of odo for macOS https://github.com/redhat-developer/vscode-openshift-tools/blob/main/src/tools.json#L19 |
So the version for MacOS does not work. Seems like it is the same issue as it is with the oc.. |
We are moving to odo 3.3.0 for the next iteration. This is the macOS binary for it https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/odo/v3.3.0/odo-darwin-amd64.tar.gz Can you check if this macOS binary works for you ? So that we understand if the issue is with binary or something else. |
Still having the same error. Look at this: https://bugzilla.redhat.com/show_bug.cgi?id=2097830 seems that the problem that is happening in the OC is caused by golang and have not beed fixed yet. Not sure how odo is implemented, but I guess the cause will be probably the same.. |
Yes, What I do on my system is I export OpenShift certificate and mark it as trusted on my system. This is described in one of the comments at https://bugzilla.redhat.com/show_bug.cgi?id=2097830#c27 |
That is true. However, that workaround only works for login with token if I am not mistaken so the issue for other login method still remains. |
If this is macOS 13 issue, we can just mark it as known issue and pin it. Hopefully by next release, the oc and odo issue will get resolved. |
I'm afraid that this is macOS general issue |
@lgrossma So let's say we use the 1.0 release and use odo 3.0 there, then it works on macOS perfectly? But when we move to 3.3.0, then the login fails on macOS (any version). If yes, then this is a blocker for the release. |
@mohitsuman exactly as you say |
@lgrossma @mohitsuman @kadel on vscode side we can use oc to login, we keep oc 4.9 and this should let us to do release. WDYT? |
Fix redhat-developer#2693. Signed-off-by: Denis Golovin <dgolovin@redhat.com>
I am going to push it master, to get new nightly build available for testing. |
@dgolovin @lgrossma @mohitsuman Guys, I do not have a mac to verify this. If someone could do that, please. |
@odockal works on my old MacOS 10. |
On MacOS when trying to login to a cluster I get this message
Failed to login to cluster 'https://api.ocp2.adapters-crs.ccitredhat.com:6443' with 'Command failed: "/Users/lgrossma/.vscode/extensions/redhat.vscode-openshift-connector-1.0.1/out/tools/darwin/odo-darwin-amd64" login https://api.ocp2.adapters-crs.ccitredhat.com:6443 -u='developer' -p='developer' --insecure-skip-tls-verify ✗ x509: “kube-apiserver-lb-signer” certificate is not trusted '!
This is probably cause by same issue as here: https://bugzilla.redhat.com/show_bug.cgi?id=2097830 and thus MacOS specific issues. However, when testing for the 1.0.0 release, login worked without problems. Maybe it is also caused by MacOS 13
The text was updated successfully, but these errors were encountered: