I connected Rancher to vSphere but was unable to create any clusters. Something broke before any vm’s could be created.
Looking at the cluster I could see some log lines flutter by for the nodes which suggested I had some network related issues.
I was unable to find the same lines logged anywhere - so a bonus question could be where I should find those lines?
After poking a bit at the system I realised that the network issue was name ambiguity.
In our advanced lab we have two different entities named advlab:
No matter which I selected in the rancher web interface the cluster yaml contains the same string:
kubectl -n fleet-default get VmwarevsphereConfig -o yaml | grep network
network:
- /ADVLAB/network/Advlab
But if I manually change the string to:
kubectl -n fleet-default get VmwarevsphereConfig -o yaml | grep network
network:
- /ADVLAB/network/Cluster01_DSwitch/Advlab
vm-creation starts working.
Surely that must be a bug?
How do I report such a thing?