source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-ffkln ` `kubectl create namespace ns-ffkln` namespace/ns-ffkln created create namespace ns-ffkln done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "0.9" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v0.9.4-beta.1` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 32.1M 100 32.1M 0 0 83.1M 0 --:--:-- --:--:-- --:--:-- 83.1M kbcli installed successfully. Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v0.9.4-beta.1 done Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) Kubernetes Env: v1.32.5-eks-5d4a308 POD_RESOURCES: No resources found found default storage class: gp3 kubeblocks version is:0.9.4 skip upgrade kubeblocks Error: no repositories to show helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check cluster definition set component name:vllm set component version No resources found no component version found unsupported component definition not found component version set replicas first:3 set replicas third:3 set minimum cmpv service version set minimum cmpv service version replicas:3 REPORT_COUNT:1 CLUSTER_TOPOLOGY: Not found topology in cluster definition vllm LIMIT_CPU:0.5 LIMIT_MEMORY:1 storage size: 20 No resources found in ns-ffkln namespace. termination_policy:WipeOut create 3 replica WipeOut vllm cluster check cluster version check cluster definition `kbcli cluster create vllm-vdkjog --termination-policy=WipeOut --cluster-definition=vllm --enable-all-logs=false --cluster-version=vllm-latest --set cpu=500m,memory=1Gi,replicas=3,storage=20Gi --namespace ns-ffkln ` Cluster vllm-vdkjog created check cluster status `kbcli cluster list vllm-vdkjog --show-labels --namespace ns-ffkln ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS vllm-vdkjog ns-ffkln vllm vllm-latest WipeOut Creating Jun 19,2025 18:13 UTC+0800 clusterdefinition.kubeblocks.io/name=vllm,clusterversion.kubeblocks.io/name=vllm-latest cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vllm-vdkjog --namespace ns-ffkln ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vllm-vdkjog-vllm-0 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-1-145.us-west-2.compute.internal/172.31.1.145 Jun 19,2025 18:13 UTC+0800 vllm-vdkjog-vllm-1 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-4-150.us-west-2.compute.internal/172.31.4.150 Jun 19,2025 18:14 UTC+0800 vllm-vdkjog-vllm-2 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-11-252.us-west-2.compute.internal/172.31.11.252 Jun 19,2025 18:16 UTC+0800 check pod status done connect unsupported engine type: vllm `kubectl get secrets -l app.kubernetes.io/instance=vllm-vdkjog` `kubectl get secrets vllm-vdkjog-conn-credential -o jsonpath="***.data.username***"` `kubectl get secrets vllm-vdkjog-conn-credential -o jsonpath="***.data.password***"` `kubectl get secrets vllm-vdkjog-conn-credential -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:;DB_PORT:;DB_DATABASE: There is no password in Type: 26. describe cluster `kbcli cluster describe vllm-vdkjog --namespace ns-ffkln ` Name: vllm-vdkjog Created Time: Jun 19,2025 18:13 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-ffkln vllm vllm-latest Running WipeOut Endpoints: COMPONENT MODE INTERNAL EXTERNAL vllm ReadWrite vllm-vdkjog-vllm.ns-ffkln.svc.cluster.local:8000 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME vllm vllm-vdkjog-vllm-0 Running us-west-2a ip-172-31-1-145.us-west-2.compute.internal/172.31.1.145 Jun 19,2025 18:13 UTC+0800 vllm vllm-vdkjog-vllm-1 Running us-west-2a ip-172-31-4-150.us-west-2.compute.internal/172.31.4.150 Jun 19,2025 18:14 UTC+0800 vllm vllm-vdkjog-vllm-2 Running us-west-2a ip-172-31-11-252.us-west-2.compute.internal/172.31.11.252 Jun 19,2025 18:16 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS vllm false 500m / 500m 1Gi / 1Gi data:20Gi kb-default-sc Images: COMPONENT TYPE IMAGE vllm vllm docker.io/apecloud/vllm:v0.2.7-amd64 Show cluster events: kbcli cluster list-events -n ns-ffkln vllm-vdkjog `kbcli cluster label vllm-vdkjog app.kubernetes.io/instance- --namespace ns-ffkln ` label "app.kubernetes.io/instance" not found. `kbcli cluster label vllm-vdkjog app.kubernetes.io/instance=vllm-vdkjog --namespace ns-ffkln ` `kbcli cluster label vllm-vdkjog --list --namespace ns-ffkln ` NAME NAMESPACE LABELS vllm-vdkjog ns-ffkln app.kubernetes.io/instance=vllm-vdkjog clusterdefinition.kubeblocks.io/name=vllm clusterversion.kubeblocks.io/name=vllm-latest label cluster app.kubernetes.io/instance=vllm-vdkjog Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=vllm-vdkjog --namespace ns-ffkln ` `kbcli cluster label vllm-vdkjog --list --namespace ns-ffkln ` NAME NAMESPACE LABELS vllm-vdkjog ns-ffkln app.kubernetes.io/instance=vllm-vdkjog case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=vllm clusterversion.kubeblocks.io/name=vllm-latest label cluster case.name=kbcli.test1 Success `kbcli cluster label vllm-vdkjog case.name=kbcli.test2 --overwrite --namespace ns-ffkln ` `kbcli cluster label vllm-vdkjog --list --namespace ns-ffkln ` NAME NAMESPACE LABELS vllm-vdkjog ns-ffkln app.kubernetes.io/instance=vllm-vdkjog case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=vllm clusterversion.kubeblocks.io/name=vllm-latest label cluster case.name=kbcli.test2 Success `kbcli cluster label vllm-vdkjog case.name- --namespace ns-ffkln ` `kbcli cluster label vllm-vdkjog --list --namespace ns-ffkln ` NAME NAMESPACE LABELS vllm-vdkjog ns-ffkln app.kubernetes.io/instance=vllm-vdkjog clusterdefinition.kubeblocks.io/name=vllm clusterversion.kubeblocks.io/name=vllm-latest delete cluster label case.name Success cluster connect kbcli unsupported engine type: vllm cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart vllm-vdkjog --auto-approve --force=true --namespace ns-ffkln ` OpsRequest vllm-vdkjog-restart-qnbq6 created successfully, you can view the progress: kbcli cluster describe-ops vllm-vdkjog-restart-qnbq6 -n ns-ffkln check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-restart-qnbq6 ns-ffkln Restart vllm-vdkjog vllm Running 0/3 Jun 19,2025 18:19 UTC+0800 check cluster status `kbcli cluster list vllm-vdkjog --show-labels --namespace ns-ffkln ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS vllm-vdkjog ns-ffkln vllm vllm-latest WipeOut Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=vllm-vdkjog,clusterdefinition.kubeblocks.io/name=vllm,clusterversion.kubeblocks.io/name=vllm-latest cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vllm-vdkjog --namespace ns-ffkln ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vllm-vdkjog-vllm-0 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-1-145.us-west-2.compute.internal/172.31.1.145 Jun 19,2025 18:22 UTC+0800 vllm-vdkjog-vllm-1 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-14-68.us-west-2.compute.internal/172.31.14.68 Jun 19,2025 18:20 UTC+0800 vllm-vdkjog-vllm-2 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-11-252.us-west-2.compute.internal/172.31.11.252 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: vllm check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-restart-qnbq6 ns-ffkln Restart vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:19 UTC+0800 check ops status done ops_status:vllm-vdkjog-restart-qnbq6 ns-ffkln Restart vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:19 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests vllm-vdkjog-restart-qnbq6 --namespace ns-ffkln ` opsrequest.apps.kubeblocks.io/vllm-vdkjog-restart-qnbq6 patched `kbcli cluster delete-ops --name vllm-vdkjog-restart-qnbq6 --force --auto-approve --namespace ns-ffkln ` OpsRequest vllm-vdkjog-restart-qnbq6 deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop vllm-vdkjog --auto-approve --force=true --namespace ns-ffkln ` OpsRequest vllm-vdkjog-stop-z4rk4 created successfully, you can view the progress: kbcli cluster describe-ops vllm-vdkjog-stop-z4rk4 -n ns-ffkln check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-stop-z4rk4 ns-ffkln Stop vllm-vdkjog vllm Running 0/3 Jun 19,2025 18:22 UTC+0800 check cluster status `kbcli cluster list vllm-vdkjog --show-labels --namespace ns-ffkln ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS vllm-vdkjog ns-ffkln vllm vllm-latest WipeOut Stopping Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=vllm-vdkjog,clusterdefinition.kubeblocks.io/name=vllm,clusterversion.kubeblocks.io/name=vllm-latest cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances vllm-vdkjog --namespace ns-ffkln ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME check pod status done check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-stop-z4rk4 ns-ffkln Stop vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:22 UTC+0800 check ops status done ops_status:vllm-vdkjog-stop-z4rk4 ns-ffkln Stop vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:22 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests vllm-vdkjog-stop-z4rk4 --namespace ns-ffkln ` opsrequest.apps.kubeblocks.io/vllm-vdkjog-stop-z4rk4 patched `kbcli cluster delete-ops --name vllm-vdkjog-stop-z4rk4 --force --auto-approve --namespace ns-ffkln ` OpsRequest vllm-vdkjog-stop-z4rk4 deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start vllm-vdkjog --force=true --namespace ns-ffkln ` OpsRequest vllm-vdkjog-start-2vk4w created successfully, you can view the progress: kbcli cluster describe-ops vllm-vdkjog-start-2vk4w -n ns-ffkln check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-start-2vk4w ns-ffkln Start vllm-vdkjog vllm Running 0/3 Jun 19,2025 18:23 UTC+0800 check cluster status `kbcli cluster list vllm-vdkjog --show-labels --namespace ns-ffkln ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS vllm-vdkjog ns-ffkln vllm vllm-latest WipeOut Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=vllm-vdkjog,clusterdefinition.kubeblocks.io/name=vllm,clusterversion.kubeblocks.io/name=vllm-latest check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vllm-vdkjog --namespace ns-ffkln ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vllm-vdkjog-vllm-0 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-11-252.us-west-2.compute.internal/172.31.11.252 Jun 19,2025 18:23 UTC+0800 vllm-vdkjog-vllm-1 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-14-68.us-west-2.compute.internal/172.31.14.68 Jun 19,2025 18:23 UTC+0800 vllm-vdkjog-vllm-2 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-1-145.us-west-2.compute.internal/172.31.1.145 Jun 19,2025 18:23 UTC+0800 check pod status done connect unsupported engine type: vllm check ops status `kbcli cluster list-ops vllm-vdkjog --status all --namespace ns-ffkln ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vllm-vdkjog-start-2vk4w ns-ffkln Start vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:23 UTC+0800 check ops status done ops_status:vllm-vdkjog-start-2vk4w ns-ffkln Start vllm-vdkjog vllm Succeed 3/3 Jun 19,2025 18:23 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests vllm-vdkjog-start-2vk4w --namespace ns-ffkln ` opsrequest.apps.kubeblocks.io/vllm-vdkjog-start-2vk4w patched `kbcli cluster delete-ops --name vllm-vdkjog-start-2vk4w --force --auto-approve --namespace ns-ffkln ` OpsRequest vllm-vdkjog-start-2vk4w deleted cluster update terminationPolicy WipeOut `kbcli cluster update vllm-vdkjog --termination-policy=WipeOut --namespace ns-ffkln ` cluster.apps.kubeblocks.io/vllm-vdkjog updated (no change) check cluster status `kbcli cluster list vllm-vdkjog --show-labels --namespace ns-ffkln ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS vllm-vdkjog ns-ffkln vllm vllm-latest WipeOut Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=vllm-vdkjog,clusterdefinition.kubeblocks.io/name=vllm,clusterversion.kubeblocks.io/name=vllm-latest check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vllm-vdkjog --namespace ns-ffkln ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vllm-vdkjog-vllm-0 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-11-252.us-west-2.compute.internal/172.31.11.252 Jun 19,2025 18:23 UTC+0800 vllm-vdkjog-vllm-1 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-14-68.us-west-2.compute.internal/172.31.14.68 Jun 19,2025 18:23 UTC+0800 vllm-vdkjog-vllm-2 ns-ffkln vllm-vdkjog vllm Running us-west-2a 500m / 500m 1Gi / 1Gi data:20Gi ip-172-31-1-145.us-west-2.compute.internal/172.31.1.145 Jun 19,2025 18:23 UTC+0800 check pod status done connect unsupported engine type: vllm cluster list-logs `kbcli cluster list-logs vllm-vdkjog --namespace ns-ffkln ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update vllm-vdkjog --enable-all-logs=true --namespace ns-ffkln Error from server (NotFound): pods "vllm-vdkjog-vllm-0" not found cluster logs `kbcli cluster logs vllm-vdkjog --tail 30 --namespace ns-ffkln ` /scripts/start.sh: line 13: curl: command not found model=../ bash: line 1: git: command not found bash: line 1: git: command not found current pod ordinal: 0 model=../ EXTRA_ARGS= 2025-06-19 10:23:51,663 WARNING utils.py:587 -- Ray currently does not support initializing Ray with fractional cpus. Your num_cpus will be truncated from 0.5 to 0. [2025-06-19 10:23:51,861 W 13 13] global_state_accessor.cc:465: Some processes that the driver needs to connect to have not registered with GCS, so retrying. Have you run 'ray start' on this node? [2025-06-19 10:23:52,862 W 13 13] global_state_accessor.cc:465: Some processes that the driver needs to connect to have not registered with GCS, so retrying. Have you run 'ray start' on this node? 2025-06-19 10:23:44,952 INFO usage_lib.py:449 -- Usage stats collection is enabled by default without user confirmation because this terminal is detected to be non-interactive. To disable this, add `--disable-usage-stats` to the command that starts the cluster, or run the following command: `ray disable-usage-stats` before starting the cluster. See https://docs.ray.io/en/master/cluster/usage-stats.html for more details. 2025-06-19 10:23:44,952 INFO scripts.py:744 -- Local node IP: 172.31.0.103 2025-06-19 10:23:53,955 SUCC scripts.py:781 -- -------------------- 2025-06-19 10:23:53,956 SUCC scripts.py:782 -- Ray runtime started. 2025-06-19 10:23:53,956 SUCC scripts.py:783 -- -------------------- 2025-06-19 10:23:53,956 INFO scripts.py:785 -- Next steps 2025-06-19 10:23:53,956 INFO scripts.py:788 -- To add another node to this Ray cluster, run 2025-06-19 10:23:53,956 INFO scripts.py:791 -- ray start --address='172.31.0.103:6379' 2025-06-19 10:23:53,956 INFO scripts.py:800 -- To connect to this Ray cluster: 2025-06-19 10:23:53,956 INFO scripts.py:802 -- import ray 2025-06-19 10:23:53,957 INFO scripts.py:803 -- ray.init() 2025-06-19 10:23:53,957 INFO scripts.py:834 -- To terminate the Ray runtime, run 2025-06-19 10:23:53,957 INFO scripts.py:835 -- ray stop 2025-06-19 10:23:53,957 INFO scripts.py:838 -- To view the status of the cluster, use 2025-06-19 10:23:53,957 INFO scripts.py:839 -- ray status 2025-06-19 10:23:53,957 INFO scripts.py:952 -- --block 2025-06-19 10:23:53,957 INFO scripts.py:953 -- This command will now block forever until terminated by a signal. 2025-06-19 10:23:53,958 INFO scripts.py:956 -- Running subprocesses are monitored and a message will be printed if any of them terminate unexpectedly. Subprocesses exit with SIGTERM will be treated as graceful, thus NOT reported. /usr/bin/python: Error while finding module specification for 'vllm.entrypoints.api_server' (ModuleNotFoundError: No module named 'vllm') /usr/bin/python: Error while finding module specification for 'vllm.entrypoints.api_server' (ModuleNotFoundError: No module named 'vllm') delete cluster vllm-vdkjog `kbcli cluster delete vllm-vdkjog --auto-approve --namespace ns-ffkln ` Cluster vllm-vdkjog deleted pod_info:vllm-vdkjog-vllm-0 1/1 Terminating 0 35s vllm-vdkjog-vllm-1 1/1 Terminating 0 33s vllm-vdkjog-vllm-2 1/1 Terminating 0 32s pod_info:vllm-vdkjog-vllm-0 1/1 Terminating 0 55s vllm-vdkjog-vllm-1 1/1 Terminating 0 53s vllm-vdkjog-vllm-2 1/1 Terminating 0 52s No resources found in ns-ffkln namespace. delete cluster pod done No resources found in ns-ffkln namespace. check cluster resource non-exist OK: pvc No resources found in ns-ffkln namespace. delete cluster done No resources found in ns-ffkln namespace. No resources found in ns-ffkln namespace. No resources found in ns-ffkln namespace. Vllm Test Suite All Done! --------------------------------------VLLM (Topology = Replicas 3) Test Result-------------------------------------- [PASSED]|[Create]|[ClusterDefinition=vllm;ClusterVersion=vllm-latest;]|[Description=Create a cluster with the specified cluster definition vllm and cluster version vllm-latest] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]