[BUG] qdrant cluster creation failed

[haowen159]

Describe the bug A clear and concise description of what the bug is.

kbcli version
Kubernetes: v1.29.6-gke.1326000
KubeBlocks: 1.0.0-alpha.4
kbcli: 1.0.0-alpha.0

To Reproduce Steps to reproduce the behavior:

1. create cluster cluster yaml:

apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":{"annotations":{},"name":"qdrant-sbxrnr","namespace":"default"},"spec":{"componentSpecs":[{"componentDef":"qdrant","name":"qdrant","replicas":2,"resources":{"limits":{"cpu":"100m","memory":"0.5Gi"},"requests":{"cpu":"100m","memory":"0.5Gi"}},"volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":null}}]}],"terminationPolicy":"Halt"}}
  creationTimestamp: "2024-08-29T06:25:16Z"
  finalizers:
  - cluster.kubeblocks.io/finalizer
  generation: 2
  name: qdrant-sbxrnr
  namespace: default
  resourceVersion: "51418584"
  uid: 6825ef4c-de9b-4267-998c-8095462b7968
spec:
  componentSpecs:
  - componentDef: qdrant
    name: qdrant
    replicas: 2
    resources:
      limits:
        cpu: 100m
        memory: 512Mi
      requests:
        cpu: 100m
        memory: 512Mi
    serviceVersion: 1.10.0
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 1Gi
  terminationPolicy: Halt
status:
  components:
    qdrant:
      podsReady: false
  conditions:
  - lastTransitionTime: "2024-08-29T06:25:16Z"
    message: 'The operator has started the provisioning of Cluster: qdrant-sbxrnr'
    observedGeneration: 2
    reason: PreCheckSucceed
    status: "True"
    type: ProvisioningStarted
  - lastTransitionTime: "2024-08-29T06:25:16Z"
    message: Successfully applied for resources
    observedGeneration: 2
    reason: ApplyResourcesSucceed
    status: "True"
    type: ApplyResources
  - lastTransitionTime: "2024-08-29T06:25:16Z"
    message: 'pods are not ready in Components: [qdrant], refer to related component
      message in Cluster.status.components'
    reason: ReplicasNotReady
    status: "False"
    type: ReplicasReady
  - lastTransitionTime: "2024-08-29T06:25:16Z"
    message: 'pods are unavailable in Components: [qdrant], refer to related component
      message in Cluster.status.components'
    reason: ComponentsNotReady
    status: "False"
    type: Ready
  observedGeneration: 2

2. see error

kbcli cluster list
NAME            NAMESPACE   CLUSTER-DEFINITION   VERSION   TERMINATION-POLICY   STATUS   CREATED-TIME                 
qdrant-sbxrnr   default                                    Halt                          Aug 29,2024 14:25 UTC+0800  

There is no status of cluster qdrant-sbxrnr. 3. describe cmp

k describe cmp qdrant-sbxrnr-qdrant
Name:         qdrant-sbxrnr-qdrant
Namespace:    default
Labels:       app.kubernetes.io/instance=qdrant-sbxrnr
              app.kubernetes.io/managed-by=kubeblocks
              apps.kubeblocks.io/cluster-uid=6825ef4c-de9b-4267-998c-8095462b7968
              apps.kubeblocks.io/component-name=qdrant
              componentdefinition.kubeblocks.io/name=qdrant
Annotations:  kubeblocks.io/generation: 2
API Version:  apps.kubeblocks.io/v1alpha1
Kind:         Component
Metadata:
  Creation Timestamp:  2024-08-29T06:25: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:                  qdrant-sbxrnr
    UID:                   6825ef4c-de9b-4267-998c-8095462b7968
  Resource Version:        51418581
  UID:                     5354d4fc-9c2d-4f49-aebd-fcbfea395aaa
Spec:
  Comp Def:  qdrant
  Replicas:  2
  Resources:
    Limits:
      Cpu:     100m
      Memory:  512Mi
    Requests:
      Cpu:     100m
      Memory:  512Mi
  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:  1.10.0
  Volume Claim Templates:
    Name:  data
    Spec:
      Access Modes:
        ReadWriteOnce
      Resources:
        Requests:
          Storage:  1Gi
Status:
  Conditions:
    Last Transition Time:  2024-08-29T06:25:16Z
    Message:               requeue after: 1s as: build synthesized component for qdrant-sbxrnr-qdrant failed: exec image and container must be the same
    Reason:                PreCheckFailed
    Status:                False
    Type:                  ProvisioningStarted
Events:                    <none>

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.