[BUG] Clickhouse cluster creation failed
Opened this issue · 0 comments
haowen159 commented
Describe the bug
A clear and concise description of what the bug is.
kbcli version
Kubernetes: v1.28.11-gke.1019001
KubeBlocks: 1.0.0-alpha.1
kbcli: 1.0.0-alpha.0
To Reproduce
Steps to reproduce the behavior:
- cluster yam
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: chouse-ocuvod
namespace: default
spec:
terminationPolicy: Delete
componentSpecs:
- name: clickhouse
componentDef: clickhouse-1.0.0-alpha.0
replicas: 2
resources:
requests:
cpu: 200m
memory: 1Gi
limits:
cpu: 200m
memory: 1Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- name: clickhouse-1
componentDef: clickhouse-1.0.0-alpha.0
replicas: 2
resources:
requests:
cpu: 200m
memory: 1Gi
limits:
cpu: 200m
memory: 1Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- name: ch-keeper
componentDef: clickhouse-keeper-1.0.0-alpha.0
replicas: 1
resources:
requests:
cpu: 200m
memory: 1Gi
limits:
cpu: 200m
memory: 1Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
2.see error. There is no status of the cluster
kbcli cluster list chouse-ocuvod
NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME
chouse-ocuvod default Delete Aug 08,2024 15:35 UTC+0800
k get cmp
NAME DEFINITION SERVICE-VERSION STATUS AGE
chouse-ocuvod-ch-keeper clickhouse-keeper-1.0.0-alpha.0 22.9.4 6m31s
chouse-ocuvod-clickhouse clickhouse-1.0.0-alpha.0 22.9.4 6m31s
chouse-ocuvod-clickhouse-1 clickhouse-1.0.0-alpha.0 22.9.4 6m31s
- describe cmp
k describe cmp chouse-ocuvod-clickhouse
Name: chouse-ocuvod-clickhouse
Namespace: default
Labels: app.kubernetes.io/instance=chouse-ocuvod
app.kubernetes.io/managed-by=kubeblocks
apps.kubeblocks.io/cluster-uid=5237e9c8-83b3-4064-a81c-bb05e69c96e6
apps.kubeblocks.io/component-name=clickhouse
componentdefinition.kubeblocks.io/name=clickhouse-1.0.0-alpha.0
Annotations: kubeblocks.io/generation: 2
API Version: apps.kubeblocks.io/v1alpha1
Kind: Component
Metadata:
Creation Timestamp: 2024-08-08T07:35:16Z
Finalizers:
cluster.kubeblocks.io/finalizer
component.kubeblocks.io/finalizer
Generation: 1
Owner References:
API Version: apps.kubeblocks.io/v1alpha1
Block Owner Deletion: true
Controller: true
Kind: Cluster
Name: chouse-ocuvod
UID: 5237e9c8-83b3-4064-a81c-bb05e69c96e6
Resource Version: 30720811
UID: 82dbacb4-3a0d-46a1-ba59-80e8f27d744d
Spec:
Comp Def: clickhouse-1.0.0-alpha.0
Replicas: 2
Resources:
Limits:
Cpu: 200m
Memory: 1Gi
Requests:
Cpu: 200m
Memory: 1Gi
Scheduling Policy:
Affinity:
Node Affinity:
Preferred During Scheduling Ignored During Execution:
Preference:
Match Expressions:
Key: kb-data
Operator: In
Values:
true
Weight: 100
Tolerations:
Effect: NoSchedule
Key: kb-data
Operator: Equal
Value: true
Service Version: 22.9.4
Volume Claim Templates:
Name: data
Spec:
Access Modes:
ReadWriteOnce
Resources:
Requests:
Storage: 20Gi
Status:
Conditions:
Last Transition Time: 2024-08-08T07:35:16Z
Message: The operator has started the provisioning of Cluster: chouse-ocuvod-clickhouse
Observed Generation: 1
Reason: PreCheckSucceed
Status: True
Type: ProvisioningStarted
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Warning 97s (x16 over 7m7s) component-controller failed to render configmap: [failed to render configuration template[cm:clickhouse-tpl][key:00_default_overrides.xml], error: [template: clickhouse-tpl:19:21: executing "clickhouse-tpl" at <$compIter.componentDefRef>: map has no entry for key "componentDefRef"]]
There is the same bug with the cmp of cmpd clickhouse-keeper-1.0.0-alpha.0
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.