paigerube14
commented
1 year ago Think this is an issue on the litmus side. We probably need to update to newer versions of litmus. Think we currently are using 1.* version and they are on 3. We are also working on taking out litmus references and add in our own, in house, versions of tests similar to this. https://github.com/redhat-chaos/krkn/blob/main/docs/arcaflow_scenarios.md#sysbench-cpu-hog
Executed this command: podman run --name=krkn --rm --net=host --env-host=true -v ${KUBECONFIG}:/root/.kube/config:Z -d -e CERBERUS_ENABLED=true -e CERBERUS_URL=http://0.0.0.0:${CERBERUS_PORT} -e TOTAL_CHAOS_DURATION=60 -e MEMORY_CONSUMPTION_PERCENTAGE=175 -e TARGET_NODES="master-1-0,master-1-1,master-1-2" quay.io/redhat-chaos/krkn-hub:node-memory-hog
Result: 2023-04-13 14:48:43,001 [INFO] Starting kraken
2023-04-13 14:48:43,014 [INFO] Initializing client to talk to the Kubernetes cluster
2023-04-13 14:48:48,556 [INFO] Fetching cluster info
2023-04-13 14:48:48,575 [INFO] Cluster version is 4.13.0-rc.0
2023-04-13 14:48:48,576 [INFO] Server URL: https://api.elvis2.qe.lab.redhat.com:6443
2023-04-13 14:48:48,576 [INFO] Generated a uuid for the run: 2a51f7db-3523-4f06-9a41-d0591d1709cf
2023-04-13 14:48:48,576 [INFO] Daemon mode not enabled, will run through 1 iterations
2023-04-13 14:48:48,576 [INFO] Executing scenarios for iteration 0
2023-04-13 14:48:48,576 [INFO] Running litmus scenarios
2023-04-13 14:48:49,382 [INFO] Deleting all litmus run objects
No resources found in sasha namespace.
2023-04-13 14:48:49,553 [INFO] output
No resources found in sasha namespace.
2023-04-13 14:48:51,712 [INFO] output
No resources found in sasha namespace.
2023-04-13 14:48:52,910 [INFO] output
2023-04-13 14:48:52,911 [INFO] Deleting all litmus experiments 2023-04-13 14:48:57,470 [INFO] Uninstalling Litmus operator
Warning: deleting cluster-scoped resources, not scoped to the provided namespace 2023-04-13 14:49:04,076 [INFO] output namespace "litmus" deleted
serviceaccount "litmus" deleted
clusterrole.rbac.authorization.k8s.io "litmus" deleted
clusterrolebinding.rbac.authorization.k8s.io "litmus" deleted
deployment.apps "chaos-operator-ce" deleted
customresourcedefinition.apiextensions.k8s.io "chaosengines.litmuschaos.io" deleted
customresourcedefinition.apiextensions.k8s.io "chaosexperiments.litmuschaos.io" deleted customresourcedefinition.apiextensions.k8s.io "chaosresults.litmuschaos.io" deleted
2023-04-13 14:49:04,077 [INFO] Deleting litmus crd
2023-04-13 14:49:04,459 [INFO] output
2023-04-13 14:49:04,459 [INFO] Installing version v1.13.8 of litmus in namespace litmus
Warning: would violate PodSecurity "restricted:latest": seccompProfile (pod or container "chaos-operator" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
Warning: would violate PodSecurity "restricted:latest": seccompProfile (pod or container "chaos-operator" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost") 2023-04-13 14:49:08,494 [INFO] Waiting for litmus operator to become available
2023-04-13 14:49:10,840 [INFO] Installing all litmus experiments
2023-04-13 14:49:30,188 [INFO] Waiting for node-memory-hog to be initialized 2023-04-13 14:49:40,212 [INFO] Waiting for node-memory-hog to be completed
2023-04-13 14:49:40,264 [INFO] Chaos scenario:nginx-chaos failed with error: failed in chaos injection phase 2023-04-13 14:49:40,265 [INFO] See 'kubectl get chaosresult nginx-chaos-node-memory-hog -n litmus -o yaml' for full results 2023-04-13 14:49:40,265 [INFO] Scenario: scenarios/memoryhog.yaml was not successfully injected, please check _
| | | | ____
| |/ / '/ ` | |/ / \ ' \
| <| | | (| | < / | | |
||__| _,||___|| |_|