Action not done in container-scenarios when action is not "kill 1" #210
Description
In https://github.com/krkn-chaos/krkn-hub/blob/main/docs/container-scenarios.md, one understands that ACTION may take values form 1 to 9.
In the demo we have ACTION="kill 1"
"kill 1" kills a container, but "kill 9" does not
"kill 1" kills a container, but "1" does not
Please advise.
Infrastructure provider
VSphere
OpenShift version
4.12.42
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
quay.io/redhat-chaos/cerberus latest 3ad8a81258d9 10 months ago 1.16 GB
quay.io/openshift-scale/kraken container-scenarios 242e805f50a2 2 years ago 2.23 GB
Running kill 1 works
export CERBERUS_ENABLED=true
export CERBERUS_URL=http://0.0.0.0:8080
export NAMESPACE=openshift-etcd
export LABEL_SELECTOR=k8s-app=etcd
export DISRUPTION_COUNT=1
export ACTION="kill 1"
export ENABLE_ALERTS=True
export EXPECTED_RECOVERY_TIME=180
export WAIT_DURATION=90 #next scenario execution looks at cerberus and expects healty clusters for OK to go signal.
export DAEMON_MODE=false
podman run --privileged \
--name=krkn \
--net=host \
--env-host=true \
-v /root/.kube/config:/root/.kube/config:Z \
-d quay.io/openshift-scale/kraken:container-scenarios
I have tried out various combinations and only "kill 1" seems to work,
export ACTION="kill 1" #it will kill
export ACTION="kill 9" #did not kill
export ACTION="1" #did not kill anything
export ACTION="kill" #did not kill anything
export ACTION="kill --signal 1" #did not kill anything
export ACTION="kill --signal SIGHUP" #did not try it because kill --signal seems not to work
export ACTION="kill --signal SIGTERM" #did not try it because kill --signal seems not to work
export ACTION="kill --signal 15" #did not try it because kill --signal seems not to work
