Open DelusionalOptimist opened 1 year ago
syscall test suit is passing in ci for k3s+docker env. https://github.com/kubearmor/KubeArmor/actions/runs/5320142460/jobs/9633972722
@rksharma95 yes, they don't fail all the time. However they fail a lot. See the attempts for this commit for example - https://github.com/kubearmor/KubeArmor/actions/runs/5241501424. Also checkout the ginkgo test runs for main branch, you'll notice that they mostly fail while running the syscalls suite - https://github.com/kubearmor/KubeArmor/actions/workflows/ci-test-ginkgo.yml?query=branch%3Amain I've also been able to reproduce it locally. Wasn't getting any logs for the SYS_UNLINK syscall. However one needs to generate some events before it happens.
Keeping it open, since it's not properly fixed
NOTE: This bug is also causing frequent failures in ginkgo tests for docker.
Bug Report
General Information
Linux kubearmor-dev-next 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Orchestration system version in use:
To Reproduce
syscall
test suite might fail. If it doesn't, runkarmor logs --gRPC=:32767 --operation=syscall --logFilter=all
, try to exec into one of the multiubuntu pods created by the above and run:Expected behavior
Should receive logs for audited syscalls.