# Failed to bring up Worker Plane

**URL:** <https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764>\
**Category:** SUSE Rancher Prime\
**Created:** [November 7, 2019, 8:05pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764 "2019-11-07T20:05:11Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 7, 2019, 8:05pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/1 "2019-11-07T20:05:11Z")

</div>

I’m trying to connect external vps to create a cluster. But whatever host I connect to, I get the following error:  
`[workerPlane] Failed to bring up Worker Plane: [Failed to verify healthcheck: Failed to check http://localhost:10248/healthz for service [kubelet] on host [xxx.xxx.xxx.xxx]: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused, log: + umount ....`  
and

`connection refused, log: I1107 20:02:46.720393 15638 aws.go:1149] Zone not specified in configuration file; querying AWS metadata service]`

It is very strange that there are almost no similar messages on the Internet, and there are no instructions about it anymore. It’s like a verdict, why nothing ever works the first time ))

I need your help. How do you know what is happening?

Thanks!

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [November 11, 2019, 3:45pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/2 "2019-11-11T15:45:17Z")

</div>

Please supply output from `docker ps -a` and `docker logs kubelet 2>&1` as this will give more info to investigate.

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 11, 2019, 7:22pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/3 "2019-11-11T19:22:50Z")

</div>

![Screenshot_4](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/4/41636febd02c27d733896becb80939c1f9622194.jpeg)

I don’t know what “aws” has to do with me not using this provider.  
???

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 11, 2019, 9:08pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/4 "2019-11-11T21:08:39Z")

</div>

This page doesn’t work:  
[https://rancher.com/docs/rancher/v2.x/en/admin-settings/rke-metadata/](https://rancher.com/docs/rancher/v2.x/en/admin-settings/rke-metadata/)

I use the vps (Virtual machines hosted by an infrastructure provider) for nodes, maybe I need to use special instructions?

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [November 12, 2019, 1:07am UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/5 "2019-11-12T01:07:12Z")

</div>

If you are running AWS EC2 instances, and you have configured your cluster with the Amazon cloud provider (in cluster options), the nodes must be able to reach EC2 metadata. If the “external vps” is not an AWS EC2 instance, you can’t join it to this cluster because of the Amazon cloud provider configuration.

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 12, 2019, 3:40am UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/6 "2019-11-12T03:40:29Z")

</div>

What does my cluster have to do with the Amazon? I don’t have any Amazon-related settings anywhere. Maybe there is a checkmark that I have not noticed in the cluster configuration tab?

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/c/cd3d7709d283ed9d8b9d68af43da58394ce24719.png)

 ![Screenshot_12](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/3/3ba0bac2073282d93f3d7abcb00c58ab874f0fdd.jpeg)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/d/d04c268890833b479c9718f7f0c68a885279a1eb.png)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/c/cdd5e764115f22ac0d0346268c7813936c74655a.jpeg)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8d8256e399e7b371a3e78a52cc46d02f06f98747.png)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/7/716194d22cc187f60ff057e8a8bbbcbcdbaed443.png)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/7/77a9b0293b2e2fcd4e2c29eb7df17384a70df910.png)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/9/993221083d66462333e539f72de083cc3368de34.jpeg)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8b7fca831898e02c456845b2dd7fbfcbdc7e8b1a.jpeg)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8a3ab26f050be5401579f9f8afd06f7f86b741d1.jpeg)

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/d/d52d456731fd211110d299c9e898314e045f8d7f.jpeg)

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [November 12, 2019, 2:12pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/7 "2019-11-12T14:12:40Z")

</div>

The configuration is described here: [https://rancher.com/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/](https://rancher.com/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers/).

It is under Cluster Options but not visible on the screenshots

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 12, 2019, 4:02pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/8 "2019-11-12T16:02:01Z")

</div>

![Screenshot_15](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/9/907d2c0d262b0696d96c0652a91e365c106165e6.jpeg)

Here’s this screen where I point to the type of node provider.

It is not clear why the cluster is trying to connect aws? Using rancher version 2.3.2.

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 12, 2019, 6:47pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/9 "2019-11-12T18:47:54Z")

</div>

![Screenshot_16](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/a/aa7674da4c90de93a937366fbfb4aff42be6eefe.jpeg)

on rancher version 2.2.9, the cluster deployed successfully.

⛔ **2.3.1 and 2.3.2 failed to launch the cluster from external nodes, referring to aws!** ⛔

I’ve published a ticket on the github:

> <https://github.com/rancher/rancher/issues/24054>
>
> \*\*What kind of request is this (question/bug/enhancement/feature request):\*\*
> bu…g
> 
> \*\*Steps to reproduce (least amount of steps as possible):\*\*
> https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/8
> 
> \*\*Result:\*\*
> 
> \[workerPlane\] Failed to bring up Worker Plane: \[Failed to verify healthcheck: Failed to check http://localhost:10248/healthz for service \[kubelet\] on host \[173.212.219.253\]: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused, log: I1109 14:21:39.331032 18794 aws.go:1149\] Zone not specified in configuration file; querying AWS metadata service\]
> 
> What does my cluster have to do with the Amazon? I don’t have any Amazon-related settings anywhere. Maybe there is a checkmark that I have not noticed in the cluster configuration tab?
> 
> 
> \*\*Environment information\*\*
> \- Rancher version (\`rancher/rancher\`): 2.3.2, 2.3.1
> \- Installation option (single install):
> docker run -d --restart=unless-stopped \\
> \-p 80:80 -p 443:443 \\
> rancher/rancher:v2.3.2 \\
> \--acme-domain my.domain.com
> 
> \<!--
> If the reported issue is regarding a created cluster, please provide requested info below
> \--\>
> 
> \*\*Cluster information\*\*
> \- Cluster type (Custom): 
> \- Machine type (VM) and specifications (CPU/memory): 4 core 8 GB
> \- Kubernetes version (use \`kubectl version\`): 1.15.5 rancher 1-2
> \- Docker version (use \`docker version\`): Docker version 18.09.7, build 2d0083d

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [November 12, 2019, 8:57pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/10 "2019-11-12T20:57:17Z")

</div>

The documentation states to configure a Kubernetes cloud provider if you want to use features from the cloud you are running on. By default, this is None. Why was it configured as `External`?

By doing a quick check it seems you get an AWS cloudprovider config when `External` is picked and saved, this needs to be investigated. If you dont want a Kubernetes cloud provider, it should be set to `None` and you shouldn’t see the error.

---

<div class="post-metadata">

**Author:** ![111](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/111/32/5926_2.png) [@111](https://forums.suse.com/u/111)\
**Post date:** [November 13, 2019, 7:36pm UTC](https://forums.suse.com/t/failed-to-bring-up-worker-plane/15764/11 "2019-11-13T19:36:33Z")

</div>

Thank you so much for your support. Launched a cluster with none setting

 ![Screenshot_23](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/3/374e91441805718660610a7124a8c706d1a461ac.jpeg)