Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready. Cluster must have at least one etcd plane host: failed to connect to the following etcd host(s) [116.203.31.240] #98

Open
egahmad opened this issue Aug 23, 2020 · 5 comments

Comments

@egahmad
Copy link

egahmad commented Aug 23, 2020

Hello,

No matter what I do I always get this error

This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Cluster must have at least one etcd plane host: failed to connect to the following etcd host(s) [116.203.31.240]

The node is created and when I delete the cluster the node got deleted but I'm always stuck at this message after several setups.

@mxschmitt
Copy link
Owner

Hi, which values did you enter in the UI?

@egahmad
Copy link
Author

egahmad commented Aug 23, 2020

It worked after detaching everything from the private network, I tried it with using the internal IP in server-url Global setting, so none of the nodes nor rancher in the private network.

The question is if I want to use the private network what is the optimum setting.

With the private network setup I tried Canal and Weave with no luck, what would be the issue?

@hco
Copy link

hco commented Oct 25, 2020

I have the same issue when I use the internal IP as server-url

@BuddhiAbeyratne
Copy link

i gave it time and it kinda worked out. its kinda a cross your fingers and pray to the DevOps gods kinda a deal

@anebi
Copy link

anebi commented Feb 12, 2021

I experienced this problem as well some time ago. If i run deployment of a new cluster, sometimes it works, but sometimes node doesn't get active. After some investigation, appeared that it has to do with Private Networking. Now I use the public ip addresses and deployment works perfectly. Somehow using Private Networking some glitches happen from time to time (not every time).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants