search

rancher / quickstart

382 stars 342 forks source link

worked fine with 1 node, changed to 3 nodes in config.yml, it seems to be stuck at provisioning #50

Closed kundeng closed 2 years ago

kundeng commented 4 years ago

I changed the config.yml to have 3 nodes. vagrant up provisions 4 servers.

https://172.22.101.101/g/clusters shows the cluster in provisioning status, but it seems to be stuck.

I vagrant ssh into one of the nodes, how do I check what is wrong?

H8to commented 4 years ago

Same here. Is this an IP clash issue? There is only one IP for node, but the count can be n?

nikkelma commented 4 years ago

The Vagrantfile increments the node's IP up from the base node IP for further nodes, see this line in the Vagrantfile.

Tested a 3-node downstream cluster today and worked - I set k8s_version to v1.16.9-rancher1-1 (to guarantee I avoided #53) and set node.count to 3 and was successful, hope this is helpful in some way.

kundeng commented 4 years ago

Were you using virtualbox for vagrant? What exactly did you change beyond setting k8s_version.

nikkelma commented 4 years ago

I used virtualbox for vagrant on my Mac, and I only changed the two fields I mentioned in config.yaml. Can you spin up a fresh vagrant quickstart to see if it works? Could be a good idea to ensure the old vagrant deployment is fully destroyed, too.

bashofmann commented 2 years ago

Closing, because it does not seem to be reproducible. Please re-open with more details if this is still an issue.