Beaker job not cancelled if up is killed

[johnbieren]

Describe the bug
A clear and concise description of what the bug is.
If you do a linchpin up to provision a machine in Beaker and that up command is killed, the Beaker job is left running. However, you will get no inventory back to work with it (which is probably expected). The bug is that even with the rundb, you cannot tear it down. Calling linchpin destroy with the resulting rundb will do nothing, so when using automation, the beaker job is just left alive until someone goes and manually kills it.

To Reproduce
Steps to reproduce the behavior:

1. Create a Jenkins job with say a 1h timeout
2. Create a pinfile with a beaker target that has a timeout >1h
3. Run the jenkins job that does a linchpin up
4. Let the job timeout
5. Even if you have it in a try catch with linchpin destroy, the beaker job is not cancelled

Expected behavior
A clear and concise description of what you expected to happen.
The beaker job is cancelled