rancher: Unable to get past cluster creation when using vSphere provider.
[controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver].
I can connect to the console on the VM and get an OK response when using CURL.
Please let me know if there is more information I can provide. I have been trying to deploy a cluster with multiple releases of Rancher2.0 for a few days now.
Things I have tried: vSphere 6.5 cluster vSphere 6.5 cluster, more resources per node in cluster vSphere 6.5 cluster, a single node in cluster
I have also tried the items above on a single ESXi host.
| Useful | Info |
|---|---|
| Versions | Rancher master UI: v2.0.28 |
| Access | local admin |
| Route | authenticated.cluster.index |
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 22 (3 by maintainers)
We’re working on it, this isn’t closed, and we never claimed it was fixed yet.
Master 4/20/18. Sat down with Vincent and validated ability to create a new vSphere cluster. Cluster/Notes reach active status.
@gaui There have been ~50 commits to
mastersince that commit. If you can test the latest master, that would help.@krishofmans Try this one: https://github.com/gaui/boot2docker-rootfs-mount-fix/releases/tag/17.03.2-ce
@jbalonso Fixed in master d62c1a9
vSPhere isn’t working due to this: https://github.com/rancher/rancher/issues/12205