chaosblade
chaosblade copied to clipboard
stat /opt/chaosblade/blade: no such file or directory: unknown
Issue Description
run
blade c k8s pod-cpu fullload --cpu-percent 95 --names puyiwm-pay-c4c67d86f-kht87 --namespace test-college --kubeconfig ~/.kube/config
throw error
{"code":54000,"success":false,"error":"
pods/exec: k8s exec failed, err: Internal error occurred: error executing command in container: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec \"1594d158946ac98c1074d5ea719d7fff9045c99a739003086224a6f924c31756\": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: \"/opt/chaosblade/blade\": stat /opt/chaosblade/blade: no such file or directory: unknown","result":{"uid":"1628fb56ee5fdfc4","success":false,"error":"
pods/exec: k8s exec failed, err: Internal error occurred: error executing command in container: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec \"1594d158946ac98c1074d5ea719d7fff9045c99a739003086224a6f924c31756\": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: \"/opt/chaosblade/blade\": stat /opt/chaosblade/blade: no such file or directory: unknown","statuses":[{"state":"Error","error":"
pods/exec: k8s exec failed, err: Internal error occurred: error executing command in container: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec \"1594d158946ac98c1074d5ea719d7fff9045c99a739003086224a6f924c31756\": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: \"/opt/chaosblade/blade\": stat /opt/chaosblade/blade: no such file or directory: unknown","success":false,"kind":"pod","identifier":"test-college/eklet-subnet-ghypmgac/puyiwm-pay-c4c67d86f-kht87/puyiwm-pay/8af0685e8a6c260f3bd61c5da7d30361ce26aa56bb1c54d23291613535b561bd/containerd"}]}}
Describe what happened (or what feature you want)
run script
Describe what you expected to happen
How to reproduce it (as minimally and precisely as possible)
Tell us your environment
tencent cloud
Anything else we need to know?
Check that the chaosblade daemonset has been successfully deployed
I have successfully deployed chaosblade-operator and chaosblade-tool by Helm. Do I need to deploy anything else
I have successfully deployed chaosblade-operator and chaosblade-tool by Helm. Do I need to deploy anything else
that is all. Which chaosblade version do you used?
This error often occurs when chaosblade-tool is not covered on the node. please double-check that the node where the pod is running does not cover the daemonset pod.