-
Notifications
You must be signed in to change notification settings - Fork 237
Open
Description
Describe the bug
A clear and concise description of what the bug is.
kbcli version
Kubernetes: v1.30.4-vke.4
KubeBlocks: 1.0.0-beta.41,0.9.4-beta.10
kbcli: 1.0.0-beta.20
To Reproduce
Steps to reproduce the behavior:
- install qdrant addon
helm list -n kb-system
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-qdrant kb-system 2 2025-04-02 14:24:59.566767 +0800 CST deployed qdrant-0.9.1 1.10.0
- create cluster
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: qdrant-cluster
namespace: default
spec:
clusterDefinitionRef: qdrant
topology: cluster
terminationPolicy: WipeOut
componentSpecs:
- name: qdrant
serviceVersion: 1.5.0
replicas: 2
serviceAccountName: kb-qdrant-cluster
resources:
requests:
cpu: 100m
memory: 0.5Gi
limits:
cpu: 100m
memory: 0.5Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- install kb 1.0.0-beta.41
- install qdrant kakfa 1.0.0-alpha.0
helm list -n kb-system-new
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-qdrant kb-system-new 1 2025-04-03 10:28:16.936306 +0800 CST deployed qdrant-1.0.0-alpha.0 1.10.0
- upgrade cluster to v1
helm list -n kb-system-new
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-qdrant kb-system-new 1 2025-04-03 10:28:16.936306 +0800 CST deployed qdrant-1.0.0-alpha.0 1.10.0
- see error
➜ ~ kubectl get cluster qdrant-cluster
NAME CLUSTER-DEFINITION TERMINATION-POLICY STATUS AGE
qdrant-cluster qdrant WipeOut Updating 21h
➜ ~
➜ ~ kubectl get pod -l app.kubernetes.io/instance=qdrant-cluster
NAME READY STATUS RESTARTS AGE
qdrant-cluster-qdrant-0 2/2 Running 0 21h
qdrant-cluster-qdrant-1 1/2 Running 17 (25s ago) 85m
logs errror pod
kubectl logs qdrant-cluster-qdrant-1 --previous
Defaulted container "qdrant" out of: qdrant, kbagent, qdrant-tools (init), init-kbagent (init), kbagent-worker (init)
BOOTSTRAP_HOSTNAME: .default.svc
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: .default.svc
INFO: wait for bootstrap node starting...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: .default.svc
INFO: wait for bootstrap node starting...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: .default.svc
...
INFO: wait for bootstrap node starting...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: .default.svc
INFO: wait for bootstrap node starting...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: .default.svc
INFO: wait for bootstrap node starting...
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.
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't workingSomething isn't working