[Cannot Configure Databricks with Azure CLI or Profile. 'Login error {}']
drewbeno123 opened this issue · 11 comments
Describe the bug
Whenever I try to Configure Databricks with the extension. It says it works but then the blue bar just spins forever and i get 'Login error{}' and it never connects.
To Reproduce
Steps to reproduce the behavior:
- Click on configure Databricks
- Connect with Azure CLI or Profile doesnt matter which one I use
- It says succesfully connected
- then it says 'Login error {}' and it never connects
Screenshots
If applicable, add screenshots to help explain your problem.
System information:
- Paste the output ot the
Help: About
command (CMD-Shift-P).
Version: 1.78.0 (user setup)
Commit: 252e5463d60e63238250799aef7375787f68b4ee
Date: 2023-05-03T20:09:00.748Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: Yes - Databricks Extension Version
v0.3.12
Databricks Extension Logs
Please attach the databricks extension logs
Additional context
I don't think it is a vs code error because the extension works when I connect to a different workspace. What kind of setting in my Azure environment or my Databricks workspace could cause this error?
same issue
Same problem here
Having the same issue after setting up .databrickscfg and can't connect to the workspace.
Hi. This was an issue should be fixed with this b1a234f. We are doing a new release today with this patch. Please try it out and let us know if you still see this error.
Thank you @kartikgupta-db I will let you know if it works!
Same issue here. Will try again after v0.3.13 release
Describe the bug
Whenever I try to Configure Databricks with the extension. It says it works but then the blue bar just spins forever and i get 'Login error{}' and it never connects.
To Reproduce
Steps to reproduce the behavior:
Click on configure Databricks
Connect with Azure CLI
It says succesfully connected
then it says 'Login error {}' and it never connects
Screenshots
If applicable, add screenshots to help explain your problem.
System information:
Version: 1.78.1 (user setup)
Commit: 6a995c4f4cc2ced6e3237749973982e751cb0bf9
Date: 2023-05-04T09:48:08.683Z
Electron: 22.5.1
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
Same issue, it started after I upgraded vscode 1.7.2 to 1.7.3 and persists on 1.8
Same issue here
The release got delayed. It will be happening today.
Hi everyone. The patch went out with version 0.3.13. Please update the extension to this version and see if it fixes the issue.
@kartikgupta-db It worked! V 0.3.13 fixes this issue. Thank you so much for all the help, I really appreciate how quickly you were able to get out a patch!