-
Notifications
You must be signed in to change notification settings - Fork 60
Launching Developer Sandbox feature does not work #2474
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
Comments
@worldofgeese thank you for reporting this issue. Could you run and attach error log to the issue? There should be plenty of error not related to the extension. Please look for entries where 'redhat' is part of filename in stacktrace. |
@dgolovin hi there. I opened DevTools, navigated to Console and observed output as I went through the steps outlined in my first comment. First there's a print out of my
Am I missing a bit of a log somewhere? This is all I was able to observe. I have web connectivity from the rest of VS Code whether I am in a WSL session or not so this doesn't appear to be an issue of DNS. |
@worldofgeese thank you for info.The problem is that VSCode API call to get auth session never resolves. That could be Windows 11 related issue. I'll add timeout and error handling to see what is going on. Will also find Windows 11 host to test. |
@worldofgeese I have tested this on Windows 11 and the only way I can replicate is when I let vscode open authentication page in browser and then just close it and do nothing. In this case call to vscode auth API never returns until I restart vscode. This is known behavior and nothing can be done about that at this point. There is no API to end stalled auth API requests. |
I can make a screencast of my flow for you so you can compare if the behavior on my system is different from your own? Would that be helpful? |
@worldofgeese if you can share the screencast, we can refer to which step it is failing and if there is no workaround we would add information to users so that it becomes easy for them. So please share the screencast if possible for you. |
This isn't really helpful and I apologize but this is everything I get. No browser window ever opens to continue auth. |
I should mention too that behavior is the same across both WSL and non-WSL sessions of VS Code. |
@worldofgeese it is helpful, thank you for your time spent to report this. I see the error about waiting for authentication provider time out to register. Will try to figure out why this is happening and add appropriate error reporting if possible. |
@worldofgeese I traced that error to authenticationService.ts#L685. Extension that registers authentication provider for Red Hat implemented the way it is recomended by Microsoft, so this problem should never be happening, but it is. I wonder if the same issue affects other authentication providers. Could you please check if github authentication provider works for you? Just try to use Git: Clone from palette |
@worldofgeese is there anything relevant in |
@dgolovin I can confirm I am able to authenticate to GitHub successfully through the command palette.
Where can I find this? This is what my integrated terminal looks like in VS Code |
@worldofgeese thanks for verifying github auth provider. At this point I am just trying to understand if that affects all auth providers or only Red Hat one. It seems to affect only Red Hat one. On your screenshot Terminal view is active, to see Red Hat authentication output, select Output view (second item on the left from Terminal) and then select Red Hat Authentication from combo on the right side of the Output view. |
@dgolovin oh there is no Red Hat Authentication output. Here you can see what Tasks are available: |
@worldofgeese that means Red Hat Authentication Extension is not installed. I think I know why. Could you please install it and see if that fixes the issue. You need to close the opened |
This PR fixes redhat-developer#2474. Signed-off-by: Denis Golovin [email protected]
This PR fixes #2474. Signed-off-by: Denis Golovin [email protected]
@worldofgeese unfortunately, steps above won't help. Because even if Red Hat Authentication installed it is not going to be activated in this use case. To activate it you need to:
|
Verified latest build from main branch. it works as expected. Fix is going to be released in v0.6.0. |
@dgolovin hey glad I can be of service 😄. Your fix does indeed allow me to auth to a following challenge screen that requires a SMS code. I receive the SMS code to my number however Connector never requests it, instead timing out. Here is a GIF showing the flow with a fake number entered: |
@worldofgeese I opened new issue for this one #2514 |
@worldofgeese Thanks for helping us to make the extension better and workflow smoother. The extension version 0.6.0 is released in Marketplace, can you please and see if the scenarios work for you. https://marketplace.visualstudio.com/items?itemName=redhat.vscode-openshift-connector |
@mohitsuman I can confirm it works! I am able to log in, pass the SMS challenge, and create a cluster all through the extension. However, some buttons and fields don't appear to be compatible with my dark theme, Dracula. See examples below: |
I appear to be encountering more errors as I only tested up until the Login to Sandbox action. Today, when I copied the I tried this twice without success. I also disabled my VPN the second time. |
@worldofgeese could you copy login command from console dashboard again, and run it in cmd or powershell with 'oc' replaced to line "C:\Users\Tao Hansen\.vscode\extensions\redhat.vscode-openshift-connector-0.6.0-win32-x64\out\tools\oc.exe" keep double quotes (because you have space in your profile location). |
@dgolovin I needed to alter the path and quotes a bit to get it working but it does log me in:
|
@dgolovin have you had a chance to look at this since? I can log in from the CLI but not the extension |
@worldofgeese We have fixed the compatibility of the phone number drop-down in alignment with vscode themes. This will be there in the 0.7.0 release coming out on 26 Sept. |
@mohitsuman I have discovered a new issue when copying my login command code. Please see my comments above for details. |
@worldofgeese just did the test with space in user name.
Am I missing something? Are you running exact the same command you posted above without surrounding oc.exe path with double quotes? |
Does it work when you run it like this? What is the output?
That is exactly how it is executed in vscode. |
@dgolovin if I run it exactly as you've formatted (whether with $TOKEN literally or with the actual
Yes, exactly just with $TOKEN replaced by my token like so: I just tested again and my formatted command exactly as I've described works:
|
I will be away on meditation retreat for ten days and unreachable 🧘♂️ |
With OpenShift Toolkit version 0.7.0 I am now able to successfully create and login to a Developer Sandbox cluster entirely through the extension-driven flow. |
I installed the OpenShift Connector today. If I navigate to the OpenShift extension icon, then Add OpenShift Cluster, then Start your OpenShift experience, I receive a "Detecting Authentication Session" message with a spinning widget that never resolves.
This is on Windows 11. I have tried both inside and outside a WSL session.
Screenshots of flow attached:




The text was updated successfully, but these errors were encountered: