search

googlecodelabs / feedback

Provide feedback to our codelabs by filing an issue here
18 stars 22 forks source link

[cloud-compute-the-cosmos]: cannot SSH into VM on page 8 #330

Open ptn24 opened 6 years ago

ptn24 commented 6 years ago 
Updating project ssh metadata...|Updated [https://www.googleapis.com/compute/v1/projects/gce-codelab-180106].
Updating project ssh metadata...done.
Waiting for SSH key to propagate.
Warning: Permanently added 'compute.7124039922276387821' (ECDSA) to the list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
ERROR: (gcloud.compute.ssh) Could not SSH into the instance.  It is possible that your SSH key has not propagated to the instance yet. Try runnin
g this command again.  If you still cannot connect, verify that the firewall and instance are set to accept ssh traffic.
ptnguyen2598@gce-codelab-180106:~$ gcloud compute ssh codelab-node
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ptnguyen2598@gce-codelab-180106:~$ gcloud compute ssh codelab-node
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
ptnguyen2598@gce-codelab-180106:~$ gcloud compute ssh codelab-node
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Conan776 commented 6 years ago

I'm seeing the exact same problem, even after a few clean restarts.

Trying to manually connect to the instance via the ssh connect button on my project's instance webpage under https://console.cloud.google.com/ yields a pop up with the cryptic message:

"VM guest environment outdated The VM guest environment is outdated and only supports the deprecated 'sshKeys' metadata item. Please follow the steps here to update. [Close]"

But then the window does get me to a command prompt, from where it seems possible to continue with the codelab, but... an introductory lesson shouldn't require jumping through hoops, imo.

(Trying to update the guest environment — which seemed to call for the extra step of cleaning out the yum cache — looked AOK but start/stopping the instance ultimately just nuked the web ssh access too, FWIW.)

Unfortunately, no one at Google seems to be minding the store....