Closed tuxiem closed 3 years ago
This sounds like this problem... Did you run though these steps?
https://github.com/kubernetes/cloud-provider-vsphere/blob/master/docs/book/known_issues.md
This sounds like this problem... Did you run though these steps?
https://github.com/kubernetes/cloud-provider-vsphere/blob/master/docs/book/known_issues.md
@tuxiem were you able to give this a try?
Sorry for the late reply. The known issue guide you linked to, was the correct answer to our issue :)
Thanks for the help.
Is this a BUG REPORT or FEATURE REQUEST?: /kind bug
What happened: After installing cloud-provider-vsphere, not all VMs can be provisioned, as the CPI cannot find a suitable IP, even though vSphere lists an IP on the VMs. VM's where several interfaces are listed, works correctly.
VM that won't work:
VM that works as expected:
What you expected to happen: The lookup gives a more precise error description of what action needs to be done. And Either a method on how to fix the missing interfaces in the VM, described in the docs/deployment guide. Or Fix the govc lookup, if everything fails in
VirtualMachines[].Guest.Net[].IpAddress[]
it should try to useVirtualMachines[].Guest.IpAddress
before giving up. (depends ofc on how the communication is handled within k8s for the CPI)How to reproduce it (as minimally and precisely as possible): Install a linux VM with docker as the container engine, where only one interface is present in vSphere. In the linux VM several interfaces should be present. In govc, lookup the machine.
VirtualMachines[].Guest.Net[].IpAddress[]
- should return nullVirtualMachines[].Guest.IpAddress
- should return an IPDeploy using https://github.com/kubernetes/cloud-provider-vsphere/blob/master/docs/book/tutorials/kubernetes-on-vsphere-with-kubeadm.md and https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/v2.0.0/vsphere-67u3/vanilla
Anything else we need to know?: Work-a-round, a reinstall of the VM might fix the issue with interfaces.
Environment: