Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
m
millions-ocean-48249
03/06/2023, 8:50 PMI am unable to get a custom hybrid (linux/windows) rke2 cluster working with the vSphere cloud provider/ vSphere csi enabled. The Windows nodes never get initialized... Can someone point me in the right direction here?
linux rke2 version: v1.24.9+rke2r2windows rke2 version: v1.24.9rancher version: 2.7.1vsphere version: 7.0.3linux nodes: ubuntu 22.04 (open-vm-tools)windows nodes: windows server core 2019 ltsc (vmtools version:12320)I0303 16:39:27.155021 1 node_controller.go:391] Initializing node sre-b89d40bd1vq with cloud provider
I0303 16:39:27.155095 1 search.go:76] WhichVCandDCByNodeID nodeID: sre-b89d40bd1vq
I0303 16:39:27.181513 1 search.go:208] Found node sre-b89d40bd1vq as vm=VirtualMachine:vm-18616 in vc=x.x.x.x and datacenter=dc1
I0303 16:39:27.181675 1 search.go:210] Hostname: SRE-B89D40BD1VQ, UUID: 4211dcfa-7a40-fae2-bd0c-d694c118c50b
I0303 16:39:27.181764 1 nodemanager.go:127] Discovered VM using FQDN or short-hand name
E0303 16:39:27.187892 1 node_controller.go:213] error syncing 'sre-b89d40bd1vq': failed to get provider ID for node sre-b89d40bd1vq at cloudprovider: failed to get instance ID from cloud provider: VM GuestNicInfo is empty, requeuingthe only thing I have noticed that is a bit odd, is once I run the command to connect the windows nodes to the cluster, vmtools stops reporting the IP in the UI. I am not sure if this is something related to the cni that gets created potentially or what.
I am using calico as required in the documentation.
c
creamy-pencil-82913
03/06/2023, 9:02 PMthe vmware docs suggest that this is an issue with the vmware tools installed on your Windows nodes
https://kb.vmware.com/s/article/81054
• From the host vSphere API, VM GuestInfo.net is empty NicInfo array while GuestInfo.ipAddress exists
• From the vCenter Server UI, the VM summary tab does not show a VM IP address
> Cause
This issue occurs when there are too many network interface entries found in guest OS by VMware Tools (version 10.2.0 and later).
m
millions-ocean-48249
03/06/2023, 9:16 PMhi @creamy-pencil-82913 thank you for the response. I will test adding a config file entry to ignore other interfaces.
out of curiosity is this something others have reported experiencing when setting up hybrid clusters?
c
creamy-pencil-82913
03/06/2023, 9:20 PMI’ve not seen a report of that before, no