You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like in an interactive cluster it will set the host correctly and get a bearer token all transparently as expected. For some reason the host is not set when running the same notebook in a job cluster, causing all attempts to use the WorkspaceClient with the host set to https://none/. Same user for both the interactive and job clusters and both running 12.2LTS.
I've also tried directly setting host=https:... in the WorkspaceClient() initialisation but the runtime auth seems to ignore that.
The text was updated successfully, but these errors were encountered:
Seems like in an interactive cluster it will set the host correctly and get a bearer token all transparently as expected. For some reason the host is not set when running the same notebook in a job cluster, causing all attempts to use the WorkspaceClient with the host set to https://none/. Same user for both the interactive and job clusters and both running 12.2LTS.
I've also tried directly setting host=https:... in the WorkspaceClient() initialisation but the runtime auth seems to ignore that.
The text was updated successfully, but these errors were encountered: