vSphere Provider setup is valid error on template deployment: please specify a datacenter #409
Comments
|
I wonder if the error message is incorrect. It looks like you didn't specify the full path on network for one thing and the server setting looks suspicious. Is your server really named |
No, I just changed it for pasting it here. Listing the FQDN here isn't that bad since it's not publicly resolvable/reachable anyway. The FQDN I put, and also the correct one, is |
|
Hi @MasterWayZ ! I notice that you've set |
Yes, it has a self-signed certificate that was created during its installation by itself. It's my homelab's vCenter, so I never changed the cert and just click through certificate warnings. |
|
Could you retry the cluster creation providing the full path of the network in the cluster config? |
|
Any progress with this? If you run the CLI with full logging |
|
I wonder if providing a thumbprint would help. |
|
My bad for the delay! |
|
Seems like a bug in the code while creating the ova template here: We use the For now, can you try importing the ova manually, instructions here: https://anywhere.eks.amazonaws.com/docs/reference/vsphere/vsphere-ovas/ |
I tried this, but it fails. |
|
Entry in the config yaml is: |
|
Do you mind posting the whole cluster config here? Also, vSphere has an implicit folder path for virtual machines |
|
Oh, whoops. apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
name: mmg-test
spec:
clusterNetwork:
cni: cilium
pods:
cidrBlocks:
- 10.69.0.0/16
services:
cidrBlocks:
- 10.112.0.0/12
controlPlaneConfiguration:
count: 2
endpoint:
host: "10.96.78.5"
machineGroupRef:
kind: VSphereMachineConfig
name: mmg-test-cp
datacenterRef:
kind: VSphereDatacenterConfig
name: mmg-test
externalEtcdConfiguration:
count: 3
machineGroupRef:
kind: VSphereMachineConfig
name: mmg-test-etcd
kubernetesVersion: "1.21"
workerNodeGroupConfigurations:
- count: 2
machineGroupRef:
kind: VSphereMachineConfig
name: mmg-test
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: VSphereDatacenterConfig
metadata:
name: mmg-test
spec:
datacenter: "ZB"
insecure: true
network: "eks-mmgtest"
server: "vcenter.internal.masterwayz.nl"
thumbprint: ""
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: VSphereMachineConfig
metadata:
name: mmg-test-cp
spec:
datastore: "ESXi 3/ESXi3 SSD 3"
template: "/ZB/vm/bottlerocket-vmware-k8s-1.21"
diskGiB: 25
folder: ""
memoryMiB: 8192
numCPUs: 2
osFamily: bottlerocket
resourcePool: "COMG3/Resources"
users:
- name: ec2-user
sshAuthorizedKeys:
- ssh-pubkey-here
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: VSphereMachineConfig
metadata:
name: mmg-test
spec:
datastore: "ESXi 3/ESXi3 SSD 3"
template: "/ZB/vm/bottlerocket-vmware-k8s-1.21"
diskGiB: 25
folder: ""
memoryMiB: 8192
numCPUs: 2
osFamily: bottlerocket
resourcePool: "COMG3/Resources"
users:
- name: ec2-user
sshAuthorizedKeys:
- ssh-pubkey-here
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: VSphereMachineConfig
metadata:
name: mmg-test-etcd
spec:
datastore: "ESXi 3/ESXi3 SSD 3"
template: "/ZB/vm/bottlerocket-vmware-k8s-1.21"
diskGiB: 25
folder: ""
memoryMiB: 8192
numCPUs: 2
osFamily: bottlerocket
resourcePool: "COMG3/Resources"
users:
- name: ec2-user
sshAuthorizedKeys:
- ssh-pubkey-here
--- |
|
So the deployment worked! :) |
Awesome to hear that! |
What happened:
When trying to deploy a cluster to vSphere, it will error out on the step of deploying the template to a Content Library with:
Validation failed {"validation": "vsphere Provider setup is valid", "error": "failed deploying template: error deploying template: govc: please specify a datacenter\n", "remediation": ""}What you expected to happen:
It succeeds. From what I can see, I have a datacenter specified. My vCenter has multiple datacenters in it with clusters.
How to reproduce it (as minimally and precisely as possible):
Attempt to deploy a cluster to vSphere. vCenter version is 7.0U3 build 18700403. My vCenter has multiple datacenters in it with clusters.
My config YAML:
Anything else we need to know?:
N/A
Environment:
The text was updated successfully, but these errors were encountered: