Closed expFlower closed 1 year ago
Hello 👋
Indeed we have identified that our docker container runtime implementation of name retrieval does not returns the expected information.
PR is in progress to fix this here
Thanks for the rapid response @luphaz, will watch the fix progress. Please let us know if we can assist, thanks.
I will create a release 7.20.1
with the associated fix.
I can't guarantee it will be enough to fix the issue you are encountering as you are using an environment we are not used to disrupt (EKS with docker container runtime engine)
Feel free to reopen this issue if it does not solve it.
I will ask for more informations if it's the case at that time.
Hi @luphaz, i'm out on vacation next week so short on time but that said i've deployed v7.22.0 to our environment and i've run a quick CPU Pressure disruption, this has successfully applied pressure to the targets. I'll be doing a full validation upon return but don't anticipate issues. Thanks again for the rapid turn around 🚀
Describe the bug While executing a CPU Pressure disruption the injector fails to inject the disruption successfully.
To Reproduce Steps to reproduce the behavior:
Expected behavior The expectation is that the chaos injector finds the targets and successfully injects pressure to containers.
Screenshots The chaos-contoller correctly identifies the targets:
Pod describe:
AWS node docker info (Full Docker inspect collected and save if needed)
Environment:
local
): AWS EKSAdditional context
Injector logs: