Slice key issue

[Komal Thareja]

Hi Mike,

This could possibly be because your Bastion Key has expired. Could you please try running the  notebook jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb again?

This should renew the keys. If error persists, could you please share if you see any errors in /tmp/fablib/fablib.log

Thanks,

Komal

• This reply was modified 1 month, 2 weeks ago by Komal Thareja.

[Michael Zink]

Thanks, Komal.

I created a new bastion key but totally forgot to run the notebook.

I can run the notebook without any issue but I still cannot ssh into the VM.

Error message is pretty much still the same.

fabric@winter:KNIT10 Demo-80%$ ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@2001:48e8:6401:3:f816:3eff:fe17:f0b9
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
mzink_0011417656@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535

 

Mike

[Komal Thareja]

Hi Mike,

Could you please check following files and ensure they point to the new key and have the right bastion username?

/home/fabric/work/fabric_config/fabric_rc

/home/fabric/work/fabric_config/ssh_config

Also, just verified that the VM in question seems to have been deleted.

Thanks,

Komal

[Author]

Posts