Known issues

This section walks you through the known issues in HCE.

Copy to clipboard issue

With respect to the self-managed enterprise edition (SMP), if you try to access the SMP portal over an HTTP-based connection, the Copy to clipboard facility will not work. This facility works only when you access SMP over an HTTPS-based connection.

Status timeout check issue

For faults such as node network loss, kubelet service kill, the default status check timeout is 180 seconds. If you have specified your chaos experiment duration to be less than 180 seconds, the chaos experiment can fetch the status of the helper pod once the duration is complete, and this will be within the timeout. If the duration of the experiment is more than 180 seconds, the status check times out even before the fault completes, and this results in the fault erroring out. Experiments will fail to fetch the status of the helper pods in this case.

A solution to this is to increase the status check timeout duration so that the experiment completes and you can fetch the status of helper pods.

Enable/disable Linux resilience probe

Similar to Kubernetes probe, you can enable or disable a Linux probe from the probe table. But when you do so, two fields namely type and attempt (that have empty values) are also added to the Linux probe. When you manually edit a Linux resilience probe manifest for parameters type and attempt, the edited values will not reflect in the updated manifest. Instead, the values from the database are reflected.

For example, For a Linux experiment, if you have a probe named abc, with the following characteristics:

probe:
  - name: abc
    mode: SOT

When you enable or disable the probe, the parameters reflect as follows:

probe:
  - name: abc
    type: ""
    runProperties:
      attempt: 0
    mode: SOT