FAQs

    Q: I have deployed Chaos Mesh and created PodChaos experiments successfully, but I still failed in creating NetworkChaos/TimeChaos Experiment. The log is shown below:

    You can try using the parameter: hostNetwork, as shown below:

    1. hostNetwork: true

    You can try the following command to fix it:

    1. kind delete cluster

    then deploy again.

    Q: Experiment not working after chaos is applied

    Execute kubectl describe to check the specified chaos experiment resource.

    • If there are NextStart and NextRecover fields under spec, then the chaos will be triggered after is executed.

    • If there are no NextStart and NextRecoverfields in spec, run the following command to get controller-manager’s log and see whether there are errors in it.

      1. kubectl get pods -n yourNamespace --show-labels

    If the above steps cannot solve the problem or you encounter other related errors in controller’s log, file an issue or message us in the #project-chaos-mesh channel in the workspace.

    The chaosfs sidecar container is continuously restarting, and you might see the following logs at the current sidecar container:

    1. 2020-01-19T06:30:56.629Z    INFO    chaos-daemon    Init hookfs
    2. 2020-01-19T06:30:56.630Z    ERROR   chaos-daemon    failed to create pid file   {"error": "pid file found, ensure docker is not running or delete /tmp/fuse/pid"}
    3. github.com/go-logr/zapr.(*zapLogger).Error
    • Cause: Chaos Mesh uses Fuse to inject I/O failures. It fails if you specify an existing directory as the source path for chaos. This often happens when you try to reuse a persistent volume (PV) with the Retain reclaim policy to request a PersistentVolumeClaims (PVC) resource.
    • Solution: In this case, use the following command to change the reclaim policy to :

    Q: While trying to install chaos-mesh in OpenShift, tripped over problems regarding authorization.

    Message most looked like this:

    1.  to validate against any security context constraint: [spec.securityContext.hostNetwork:
    2.  Invalid value: true: Host network is not allowed to be used spec.securityContext.hostPID:
    3.  Invalid value: true: Host PID is not allowed to be used spec.securityContext.hostIPC:
    4.  Invalid value: true: Host IPC is not allowed to be used securityContext.runAsUser:
    5.  Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.containers[0].securityContext.volumes[1]:
    6.  Invalid value: true: Host network is not allowed to be used spec.containers[0].securityContext.containers[0].hostPort:
    7.  Invalid value: 31767: Host ports are not allowed to be used spec.containers[0].securityContext.hostPID:
    8.  Invalid value: true: Host PID is not allowed to be used spec.containers[0].securityContext.hostIPC:
    9. ......]