Open penghuazhou opened 2 years ago
Same problem for сhaos operator v1.4.0 (not sure why chaos mesh is mentioned in original description) after executing the tamper dns experiment on the pod level scope.
"action": "dns",
"error": "see resStatus for the error details",
"resStatuses": [
{
"code": 63063,
"error": "`/bin/sh -c /opt/chaosblade/bin/chaos_changedns --start --domain ya.ru --ip 10.0.0.1 --debug=false`: cmd exec failed, err: /bin/sh: 1: /opt/chaosblade/bin/chaos_changedns: not found\n exit status 127",
root@my_pod:/opt/chaosblade/bin# ls
chaos_os chaos_tcnetwork
If the same experiment is ran on the node level everything works as expected.
Type: bug report
Describe what happened (or what feature you want)
Why there not exists "/opt/chaosblade/bin/chaos_changedns"? I only install chaosblade-operator use "helm install chaos-mesh chaos-mesh/chaos-mesh -n=chaos-testing --set chaosDaemon.runtime=containerd --set chaosDaemon.socketPath=/run/containerd/containerd.sock"
Describe what you expected to happen
execute success
How to reproduce it (as minimally and precisely as possible)
What version of Kubernetes are you using?
1.20.4-aliyun.1
What version of Chaos Mesh are you using?
Controller manager Version: version.Info{GitVersion:"v2.1.1", GitCommit:"4ebd7a21520305bd0cf38e228f84ebc639aab994", BuildDate:"2021-12-10T10:27:29Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}