CPU/MEM Hog scenarios - pod generated in default namespace is not cleaned/removed #162
Description
When we trigger a cpu/mem hog scenario, one pod is scheduled in the default namespace. After the scenario is completed, this pods keeps lying there and isn't removed.
In my view, this pod should be removed/cleaned once the scenario test is completed.
To verify, after the scenario is completed run $ oc get pods -n default