search

binbeobo / google-cloud-sdk

Automatically exported from code.google.com/p/google-cloud-sdk
0 stars 1 forks source link

unable to connect to one node where as other 3 nodes connected successfully using gcloud ssh command #415

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Issue running command [gcloud compute ssh].

What steps will reproduce the problem?

gcloud compute --project "satya-mapr-h1" ssh --zone "us-central1-b" "node2"

What is the expected output? What do you see instead?

expected output is::

[root@localhost Desktop]# gcloud compute --project "satya-mapr-h1" ssh --zone 
"us-central1-b" "node4"
/root/google-cloud-sdk/lib/googlecloudsdk/api_lib/compute/base_classes.py:7: 
DeprecationWarning: the sets module is deprecated
  import sets
Warning: Permanently added '104.197.140.155' (RSA) to the list of known hosts.
[root@node2 ~]# 

Please provide any additional information below.

this is a servere problem from your side, please dont charge for me for node2, 
coz i am using the same command to connect but it is not connecting to node2

[root@localhost Desktop]# gcloud compute --project "satya-mapr-h1" ssh --zone 
"us-central1-b" "node2"
/root/google-cloud-sdk/lib/googlecloudsdk/api_lib/compute/base_classes.py:7: 
DeprecationWarning: the sets module is deprecated
  import sets
Warning: Permanently added '130.211.136.192' (RSA) to the list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
ERROR: gcloud crashed (CalledProcessError): Command '['/usr/bin/ssh', '-i', 
'/root/.ssh/google_compute_engine', '-o', 'UserKnownHostsFile=/dev/null', '-o', 
'IdentitiesOnly=yes', '-o', 'CheckHostIP=no', '-o', 'StrictHostKeyChecking=no', 
u'root@130.211.136.192']' returned non-zero exit status 255

If you would like to report this issue, please run the following command:
  gcloud feedback

Original issue reported on code.google.com by sr.ra...@gmail.com on 7 Dec 2015 at 8:12

GoogleCodeExporter commented 8 years ago 
Is this issue repeatable? Is node2 running the same VM image as the other 
nodes? It's possible that the image node2 is running does not allow root login 
via SSH.

Original comment by z...@google.com on 8 Dec 2015 at 3:36