-
Notifications
You must be signed in to change notification settings - Fork 796
Description
I attempted to install LitmusChaos 3.x on a bare-metal Linux(Debian) server running an Intel Pentium Dual Core CPU. The installation failed repeatedly because the chaos-mongodb pod entered a CrashLoopBackOff state.
Upon looking at the pod logs, I found Illegal Instruction (core dumped) errors. I verified my CPU flags using grep avx /proc/cpuinfo and confirmed that my processor lacks AVX(Advanced Vector Extensions)support. The bundled version of MongoDB(5.0+) requires AVX instructions to run, causing it to crash instantly on older hardware.
The LitmusChaos documentation(Prerequisites section) should explicitly state that the CPU must support AVX. This would prevent users with older hardware(like older Pentiums, Celerons, or some IoT devices) from attempting an incompatible installation without realizing it.
This should be added to the System Requirements or Prerequisites page in the official documentation.
How to reproduce it (as minimal as possible):
- Use a machine with a CPU that lacks AVX support ( e.g., older Intel Pentium/Atom or first-generation Celeron).
- Install LitmusChaos using the standard Helm command:
helm install chaos litmuschaos/litmus. - Observe the pod status:
kubectl get pods -n litmus. - The MongoDB pod will fail to start and enter
CrashLoopBackOffwith exit code 132(Illegal Instruction).
- OS: Debian Linus(Bare Metal)
- CPU: Intel Pentium Dual Core (No AVX flags present in
/proc/cpuinfo) - Litmus Version: 3.x