stale-magazine-62677
02/06/2023, 1:02 PMI0206 12:33:14.147902 1 serving.go:348] Generated self-signed cert in-memory
I0206 12:33:14.943719 1 requestheader_controller.go:244] Loaded a new request header values for RequestHeaderAuthRequestController
W0206 12:33:14.944385 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0206 12:33:14.945319 1 main.go:160] vsphere-cloud-controller-manager version: v1.24.2
E0206 12:33:14.946287 1 config_yaml.go:136] vsphere.conf does not have the VirtualCenter IP address specified
E0206 12:33:14.946305 1 config_yaml.go:214] validateConfig failed: vsphere.conf does not have the VirtualCenter IP address specified
W0206 12:33:14.946423 1 config.go:69] ReadCPIConfigYAML failed: vsphere.conf does not have the VirtualCenter IP address specified
E0206 12:33:14.946558 1 config.go:73] ReadConfigINI failed: 3:1: expected section header
F0206 12:33:14.946582 1 main.go:265] Cloud provider could not be initialized: could not init cloud provider "vsphere": 3:1: expected section header
The vsphere-cloud-config ConfigMap looks empty
apiVersion: v1
data:
vsphere.yaml: # Global properties in this section will be used for all specified
vCenters unless overriden in VirtualCenter section.\n\nglobal:\n secretName:
\"vsphere-cpi-creds\"\n secretNamespace: \"kube-system\"\n port: 443\n insecureFlag:
true\n\nvcenter:\n \"\":\n server: \"\"\n user: \n password: \n datacenters:\n
\ - \"\"\n
kind: ConfigMap
metadata:
annotations:
<http://meta.helm.sh/release-name|meta.helm.sh/release-name>: rancher-vsphere-cpi
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: kube-system
....
The vsphere-config-secret is populated with the correct configuration
But the vsphere-cpi-creds looks empty:
apiVersion: v1
data:
.password: ""
.username: ""
kind: Secret
metadata:
annotations:
<http://meta.helm.sh/release-name|meta.helm.sh/release-name>: rancher-vsphere-cpi
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: kube-system
Has anyone here run in to a similar issue?hundreds-twilight-31144
02/08/2023, 6:54 AMbrash-jewelry-40212
02/15/2023, 7:28 PMbrash-jewelry-40212
02/16/2023, 7:32 AMbrash-jewelry-40212
02/16/2023, 1:12 PMbrash-jewelry-40212
02/16/2023, 5:23 PMgray-psychiatrist-7159
02/17/2023, 10:00 AMgray-psychiatrist-7159
02/17/2023, 10:01 AMgray-psychiatrist-7159
02/17/2023, 10:05 AMrancher2_cluster_sync
and terraform get timeoutsgray-psychiatrist-7159
02/17/2023, 10:07 AMgray-psychiatrist-7159
02/17/2023, 10:10 AMmicroscopic-telephone-96049
02/22/2023, 4:31 PMdry-policeman-72946
03/02/2023, 4:45 PMmillions-ocean-48249
03/03/2023, 4:42 PMmillions-ocean-48249
03/03/2023, 4:42 PMI0303 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, requeuing
millions-ocean-48249
03/03/2023, 4:43 PMmillions-ocean-48249
03/03/2023, 4:44 PM$ govc <http://vm.info|vm.info> -json vm-name | jq .VirtualMachines[0].Guest | grep Net
"Net": null,
millions-ocean-48249
03/03/2023, 4:49 PMmillions-ocean-48249
03/03/2023, 10:43 PMProvisioningFailed 4s (x2 over 10s) persistentvolume-controller Failed to provision volume with StorageClass "vsphere-gold": cloud provider not initialized properly
steep-zoo-77219
03/08/2023, 6:25 PMhundreds-evening-84071
03/08/2023, 6:44 PMhundreds-evening-84071
03/08/2023, 8:16 PMsalmon-noon-33588
03/09/2023, 5:35 PMvsphere.yaml: >
# Global properties in this section will be used for all specified vCenters
unless overridden in VirtualCenter section.
hundreds-evening-84071
03/10/2023, 4:58 PMlimited-elephant-16797
03/14/2023, 9:59 AMhundreds-evening-84071
03/17/2023, 2:06 PMwhite-xylophone-9961
03/17/2023, 2:12 PMprehistoric-advantage-39331
03/17/2023, 2:41 PMbored-architect-10999
03/17/2023, 2:58 PMprehistoric-advantage-39331
03/17/2023, 3:04 PMprehistoric-advantage-39331
03/17/2023, 3:04 PM