Comment 2 for bug 1558819

I started looking in to this. When trying to kill the Linuxbridge agent, we use AsyncProcess.stop, which calls _kill_process. It looks like for failed runs, it's trying to kill the wrong pid. I added a print statement, and the pid it's trying to kill is not there, while the linuxbridge agent is alive and well with a different pid. We get a Runtime error saying that the process was not found, then utils.wait_until_true(lambda: not self.is_active()) times out as it does wait on the correct pid.