Unable to deploy a Cluster on Cloudstack (validation check failed)
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Unable to deploy a Cluster on Cloudstack
Getting the follwing exception
❯ eksctl anywhere create cluster -f eksa-mgmt-cluster2.yaml -v 4
2023-02-01T16:18:49.889+0530 V4 Logger init completed {"vlevel": 4}
2023-02-01T16:18:49.890+0530 V1 First worker node group name not specified. Defaulting name to md-0.
2023-02-01T16:18:50.173+0530 V4 Reading bundles manifest {"url": "https://anywhere-assets.eks.amazonaws.com/releases/bundles/26/manifest.yaml"}
2023-02-01T16:18:50.198+0530 V1 First worker node group name not specified. Defaulting name to md-0.
2023-02-01T16:18:50.259+0530 V2 Pulling docker image {"image": "public.ecr.aws/eks-anywhere/cli-tools:v0.14.0-eks-a-26"}
2023-02-01T16:18:53.850+0530 V3 Initializing long running container {"name": "eksa_1675248530259589341", "image": "public.ecr.aws/eks-anywhere/cli-tools:v0.14.0-eks-a-26"}
2023-02-01T16:18:54.015+0530 V4 Task start {"task_name": "setup-validate"}
2023-02-01T16:18:54.015+0530 V0 Performing setup and validations
2023-02-01T16:18:54.015+0530 V0 ❌ Validation failed {"validation": "cloudstack Provider setup is valid", "error": "validating cluster spec: CloudStack Datacenter Config is null", "remediation": ""}
2023-02-01T16:18:54.015+0530 V0 ✅ Validate certificate for registry mirror
2023-02-01T16:18:54.015+0530 V0 ✅ Validate authentication for git provider
2023-02-01T16:18:54.015+0530 V0 ✅ Create preflight validations pass
2023-02-01T16:18:54.015+0530 V4 Task finished {"task_name": "setup-validate", "duration": "97.553µs"}
2023-02-01T16:18:54.015+0530 V4 ----------------------------------
2023-02-01T16:18:54.015+0530 V4 Saving checkpoint {"file": "my-cluster-name-checkpoint.yaml"}
2023-02-01T16:18:54.015+0530 V4 Tasks completed {"duration": "285.697µs"}
2023-02-01T16:18:54.015+0530 V3 Cleaning up long running container {"name": "eksa_1675248530259589341"}
Error: validations failed
Please find the my eks-cluster.yaml
```
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
name: my-cluster-name
spec:
clusterNetwork:
cniConfig:
cilium: {}
pods:
cidrBlocks:
- 192.168.0.0/16
services:
cidrBlocks:
- 10.96.0.0/12
controlPlaneConfiguration:
count: 3
endpoint:
host: "http://10.0.33.167:8080/client/api"
machineGroupRef:
kind: CloudStackMachineConfig
name: my-cluster-name-cp
datacenterRef:
kind: CloudStackDatacenterConfig
name: my-cluster-name
externalEtcdConfiguration:
count: 3
machineGroupRef:
kind: CloudStackMachineConfig
name: my-cluster-name-etcd
kubernetesVersion: "1.23"
managementCluster:
name: my-cluster-name
workerNodeGroupConfigurations:
- count: 1
machineGroupRef:
kind: CloudStackMachineConfig
name: my-cluster-name
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: CloudStackDatacenterConfig
metadata:
name: my-cluster-name-datacenter
spec:
availabilityZones:
- account: admin
credentialsRef: global
domain: eksa
managementApiEndpoint: "http://10.0.33.167:8080/client/api"
name: az-1
zone:
name: ref-trl-4329-k-M7-kiran-chavala
network:
name: "kube-net"
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: CloudStackMachineConfig
metadata:
name: my-cluster-name-cp
spec:
computeOffering:
name: "kube"
users:
- name: admin
template:
name: "kube-template2"
diskOffering:
name: "Small"
mountPath: "/data-small"
device: "/dev/vdb"
filesystem: "ext4"
label: "data_disk"
symlinks:
/var/log/kubernetes: /data-small/var/log/kubernetes
affinityGroupIds:
- control-plane-anti-affinity
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: CloudStackMachineConfig
metadata:
name: my-cluster-name
spec:
computeOffering:
name: "kube"
users:
- name: admin
template:
name: "kube-template2"
diskOffering:
name: "Small"
mountPath: "/data-small"
device: "/dev/vdb"
filesystem: "ext4"
label: "data_disk"
symlinks:
/var/log/pods: /data-small/var/log/pods
/var/log/containers: /data-small/var/log/containers
affinityGroupIds:
- worker-affinity
userCustomDetails:
foo: bar
---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: CloudStackMachineConfig
metadata:
name: my-cluster-name-etcd
spec:
computeOffering:
name: "kube"
users:
- name: "admin"
template:
name: "kube-template2"
diskOffering:
name: "Small"
mountPath: "/data-small"
device: "/dev/vdb"
filesystem: "ext4"
label: "data_disk"
symlinks:
/var/lib: /data-small/var/lib
affinityGroupIds:
- etcd-affinity
---
```
**Environment**:
❯ eksctl version
0.127.0
❯ eksctl anywhere version
v0.14.0
Contributor guide
Research direction
Start with the Cluster and CloudStackDatacenterConfig documents in my eks-cluster.yaml and compare the datacenterRef name with the metadata.name of the datacenter object. Re-run eksctl anywhere create cluster -f eksa-mgmt-cluster2.yaml -v 4 and confirm that the CloudStack provider validation passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100