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
{{ message }}
This repository has been archived by the owner on Feb 3, 2021. It is now read-only.
Tried to SSH into cluster on Windows 10 using the following https://github.com/Azure/aztk/wiki/SparklyR-on-Azure-with-AZTK
but faced similar issue to #368:
Secrets.yaml seems to be in the right format (public-private key pair is found, password for private key accepted). But no matter if for default user "spark" or a newly created one, I am then asked for a password I never provided, and can hence not access the cluster:
C:\Users\[...] > aztk spark cluster ssh --id mycluster1
-------------------------------------------
spark cluster id: mycluster1
open webui: http://localhost:8080
open jobui: http://localhost:4040
open jobhistoryui: http://localhost:18080
plugins:
rstudio_server
- open: http://localhost:8787
ssh username: spark
connect: True
-------------------------------------------
The authenticity of host '[51.105.239.1]:50000 ([51.105.239.1]:50000)' can't be established.
ECDSA key fingerprint is SHA[...].
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[51.105.239.1]:50000' (ECDSA) to the list of known hosts.
Password:
spark@[IP]'s password:
Permission denied, please try again.
Tried to SSH into cluster on Windows 10 using the following https://github.com/Azure/aztk/wiki/SparklyR-on-Azure-with-AZTK
but faced similar issue to #368:
Secrets.yaml seems to be in the right format (public-private key pair is found, password for private key accepted). But no matter if for default user "spark" or a newly created one, I am then asked for a password I never provided, and can hence not access the cluster:
The issue persists when recreating the key-pair, or registering it on the cluster according to https://docs.quantumatk.com/_downloads/ssh_keys.pdf, p.7.
The text was updated successfully, but these errors were encountered: