Open JashBook opened 4 months ago
The error exists in v0.9.0
It appears that the addons are in the process of installation. Before the addon installation is complete, the system may experience various malfunctions and errors.
For instance, if you create a cluster during this time, you might find an event stating that 'csi-hostpath' does not exist. In reality, this occurs because the installation of the 'csi-hostpath' addon has not yet finished.
$ kubectl get events
...
3m46s Warning ProvisioningFailed persistentvolumeclaim/data-weed44-mysql-1 storageclass.storage.k8s.io "csi-hostpath-sc" not found
1s Normal ExternalProvisioning persistentvolumeclaim/data-weed44-mysql-2 waiting for a volume to be created, either by external provisioner "hostpath.csi.k8s.io" or manually created by system administrator
$ kbcli addon list
...
csi-hostpath-driver 0.7.0 community Enabling true
...
This issue has been marked as stale because it has been open for 30 days with no activity
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
addon is enable
➜ ~ kbcli addon list NAME VERSION PROVIDER STATUS AUTO-INSTALL
csi-driver-nfs 4.5.0 community Disabled false
csi-hostpath-driver 0.7.0 community Disabled false
csi-s3 0.7.0 community Disabled false
external-dns 6.20.4 community Disabled false
fault-chaos-mesh 2.5.2 apecloud Disabled false
kubebench 0.0.1 apecloud Disabled false
kubeblocks-csi-driver 0.1.4 community Disabled false
llm 0.9.0 community Disabled false
loki 5.8.9 community Disabled false
migration 0.1.1 apecloud Disabled false
minio 12.8.12 community Disabled false
nvidia-gpu-exporter 0.3.1 community Disabled false
nyancat 0.7.0 apecloud Disabled false
pyroscope-server 0.2.92 community Disabled false
qdrant 0.9.0 community Disabled false
victoria-metrics-agent 0.8.41 community Disabled false
alertmanager-webhook-adaptor 0.1.4 apecloud Enabled true
apecloud-mysql 0.9.0-beta.10 apecloud Enabled true
apecloud-otel-collector 0.1.2-beta.3 apecloud Enabled true
aws-load-balancer-controller 1.4.8 community Enabled true
kafka 0.9.0 community Enabled true
mongodb 0.9.0 apecloud Enabled true
mysql 0.9.1 community Enabled true
postgresql 0.9.0 community Enabled true
pulsar 0.9.0 community Enabled true
redis 0.9.0 community Enabled true
snapshot-controller 1.7.2 community Enabled true
grafana 6.43.5 community Enabling true
prometheus 15.16.1 community Enabling true
kubectl get cd NAME TOPOLOGIES SERVICEREFS STATUS AGE apecloud-mysql Available 2m11s kafka Available 2m9s mongodb Available 2m10s mongodb-sharding Available 2m10s mysql Available 117s postgresql Available 114s pulsar Available 2m6s pulsar-zookeeper Available 2m6s redis replication,replication-twemproxy,standalone Available 116s
➜ ~ kbcli playground destroy --purge=true --auto-approve
Warning: This action will destroy the kubernetes cluster, there may be residual resources, please confirm and manually clean up related resources after this action.
Do you really want to destroy the kubernetes cluster kb-playground-w5qkz? cloud provider: aws cluster name: kb-playground-w5qkz region: us-west-2
The operation cannot be rollbacked. Only 'yes' will be accepted to confirm.
Write kubeconfig to /Users/huangzhangshu/.kbcli/playground/kubeconfig OK Delete clusters created by KubeBlocks OK Uninstall KubeBlocks in namespace "kb-system" Wait for addons to be disabled alertmanager-webhook-adaptor Disabling apecloud-mysql Disabling apecloud-otel-collector Disabling aws-load-balancer-controller Disabling grafana Disabling kafka Disabling mongodb Disabling mysql Disabling postgresql Disabling prometheus Disabling pulsar Disabling redis Disabling snapshot-controller Disabling
Disabling addons: apecloud-mysql, apecloud-otel-collector, mysql, pulsar, snapshot-controller, aws-load-balancer-controller, mongodb, postgresql, alertmanager-webhook-adaptor, prometheus, grafana, kafka, redis Please wait for a while and try to run "kbcli addon list" to check addons status. Failed to uninstall addons, run "kbcli kubeblocks uninstall" to retry. error: context deadline exceeded