# vSphere nodes Waiting for SSH

**URL:** <https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985>\
**Category:** SUSE Rancher Prime\
**Created:** [April 17, 2019, 10:07am UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985 "2019-04-17T10:07:27Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bcalvet](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bcalvet](https://forums.suse.com/u/bcalvet)\
**Post date:** [April 17, 2019, 10:07am UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/1 "2019-04-17T10:07:27Z")

</div>

Hi, everyone . I’m new to the Rancher universe and i’m trying to deploy Kubernetes cluster on top of an vSphere infrastructure.  
I have two nodes templates using rancheros-vmware iso.  
I Provide a cloud-config.yml file with just a SSH Key.

### Rancher Version

[v2.2.2]

### Config-File

ssh\_authorized\_keys:

- ssh-rsa [My-Key]

### Image of RancherOS

[https://github.com/rancher/os/releases/download/v1.5.1/rancheros-vmware.iso](https://github.com/rancher/os/releases/download/v1.5.1/rancheros-vmware.iso)

### Logs

2019/04/17 09:50:54 [INFO] stdout: (mmm1)  
2019/04/17 09:50:54 [INFO] (mmm1)  
2019/04/17 09:50:55 [INFO] stdout: (mmm1) Waiting for VMware Tools to come online…  
2019/04/17 09:50:55 [INFO] (mmm1) Waiting for VMware Tools to come online…  
2019/04/17 09:50:56 [INFO] stdout: (www1) adding network: VLAN\_2402  
2019/04/17 09:50:56 [INFO] (www1) adding network: VLAN\_2402  
2019/04/17 09:50:56 [INFO] stdout: (www1) Reconfiguring VM  
2019/04/17 09:50:56 [INFO] (www1) Reconfiguring VM  
2019/04/17 09:50:57 [INFO] stdout: (www1) Setting disk.enableUUID to TRUE  
2019/04/17 09:50:57 [INFO] (www1) Setting disk.enableUUID to TRUE  
2019/04/17 09:50:57 [INFO] stdout: (www1) setting guestinfo.cloud-init.data.url to [http://172.16.29.61/config.yml](http://172.16.29.61/config.yml)  
2019/04/17 09:50:57 [INFO] (www1) setting guestinfo.cloud-init.data.url to [http://172.16.29.61/config.yml](http://172.16.29.61/config.yml)  
2019/04/17 09:50:57 [INFO] stdout: (www1)  
2019/04/17 09:50:57 [INFO] (www1)  
2019/04/17 09:50:58 [INFO] stdout: (www1) Waiting for VMware Tools to come online…  
2019/04/17 09:50:58 [INFO] (www1) Waiting for VMware Tools to come online…  
2019/04/17 09:51:57 [INFO] stdout: (mmm1) Provisioning certs and ssh keys…  
2019/04/17 09:51:57 [INFO] (mmm1) Provisioning certs and ssh keys…  
2019/04/17 09:51:58 [INFO] stdout: Waiting for machine to be running, this may take a few minutes…  
2019/04/17 09:51:58 [INFO] Waiting for machine to be running, this may take a few minutes…  
2019/04/17 09:51:58 [INFO] stdout: Detecting operating system of created instance…  
2019/04/17 09:51:58 [INFO] Detecting operating system of created instance…  
2019/04/17 09:51:58 [INFO] stdout: Waiting for SSH to be available…  
2019/04/17 09:51:58 [INFO] Waiting for SSH to be available…  
2019/04/17 09:52:07 [INFO] stdout: (www1) Provisioning certs and ssh keys…  
2019/04/17 09:52:07 [INFO] (www1) Provisioning certs and ssh keys…  
2019/04/17 09:52:08 [INFO] stdout: Waiting for machine to be running, this may take a few minutes…  
2019/04/17 09:52:08 [INFO] Waiting for machine to be running, this may take a few minutes…  
2019/04/17 09:52:08 [INFO] stdout: Detecting operating system of created instance…  
2019/04/17 09:52:08 [INFO] Detecting operating system of created instance…  
2019/04/17 09:52:08 [INFO] stdout: Waiting for SSH to be available…  
2019/04/17 09:52:08 [INFO] Waiting for SSH to be available…

So I get my nodes into provisionning state, stuck on **Waiting for SSH to be available…**  
From the host running Rancher container, I can ssh the nodes created as rancher user, but it asks for password.  
Also the .ssh/authorized\_keys from both root and rancher is empty (not created).

Do you guys have any idea ?

Kind Regards.

---

<div class="post-metadata">

**Author:** ![nkumar](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/nkumar/32/5111_2.png) [@nkumar](https://forums.suse.com/u/nkumar)\
**Post date:** [April 24, 2019, 6:02am UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/2 "2019-04-24T06:02:29Z")

</div>

I’m running into the same issue. No idea on how to get this to work…

---

<div class="post-metadata">

**Author:** ![Odiobill](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@Odiobill](https://forums.suse.com/u/Odiobill)\
**Post date:** [December 31, 2019, 10:32am UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/3 "2019-12-31T10:32:04Z")

</div>

Same issue here as well, even without providing a custom cloud-config.yml. It keeps being stuck on “Waiting for SSH to be available…”. After a while, it looks like some timeouts happen, and it tries again from the beginning, but without any better luck. Using Rancher 2.3.2.

I know this is quite an old thread, but is there any chance to receive some hints in order to solve this issue?

---

<div class="post-metadata">

**Author:** ![kataliyst](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kataliyst](https://forums.suse.com/u/kataliyst)\
**Post date:** [April 24, 2020, 6:35pm UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/4 "2020-04-24T18:35:04Z")

</div>

Same issue here… would be great to have some help.

2020/04/24 17:22:13 [INFO] [node-controller-rancher-machine] Waiting for machine to be running, this may take a few minutes…  
2020/04/24 17:22:13 [INFO] [node-controller-rancher-machine] Detecting operating system of created instance…  
2020/04/24 17:22:13 [INFO] [node-controller-rancher-machine] Waiting for SSH to be available…

---

<div class="post-metadata">

**Author:** ![kataliyst](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kataliyst](https://forums.suse.com/u/kataliyst)\
**Post date:** [April 27, 2020, 8:42pm UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/5 "2020-04-27T20:42:04Z")

</div>

Error creating machine: Error running provisioning: ssh command error: command: sudo systemctl -f start docker err: exit status 1 output: Job for docker.service failed because the control process exited with error code.

---

<div class="post-metadata">

**Author:** ![kataliyst](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kataliyst](https://forums.suse.com/u/kataliyst)\
**Post date:** [April 27, 2020, 8:53pm UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/6 "2020-04-27T20:53:14Z")

</div>

Found this:  
[https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1844894](https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1844894)

After a fresh install with docker never installed - this issue is resolved. docker installs.

---

<div class="post-metadata">

**Author:** ![BillGunter](https://avatars.discourse-cdn.com/v4/letter/b/dbc845/32.png) [@BillGunter](https://forums.suse.com/u/BillGunter)\
**Post date:** [March 19, 2021, 11:40am UTC](https://forums.suse.com/t/vsphere-nodes-waiting-for-ssh/13985/7 "2021-03-19T11:40:11Z")

</div>

In my case (rancher v2.5.5) the provisioner is trying to login as the docker user, but that user doesn’t exist on the provisioned node. The docker install doesn’t seem to add it, so where is that user meant to come from?
