redhat-performance/JetSki

Use only non-containerized method to run badfish

dustinblack opened this issue · 1 comments

Running badfish in a container via an ansible task has shown to sometimes cause an infinite hang when the badfish command within its pod fails and the pod execution doesn't return. This was solved in the shared-labs-prep role by cloning badfish and executing it directly, but the containerized method still exists in the bootstrap role.

We should correct the bootstrap role to use badfish without a container, and we should implement this such that we are not duplicating the code between the roles.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days