run_utah_tests can grab an old output file if utah client fails

I found that when using run_utah_tests with --skip-provisioning on an already provisioned machine, if I get an error that causes the utah client not to generate normal output (i.e., a bad tc_control file,) and output is present from a previous run, that gets pulled back. We should probably overwrite that output file when a failure occurs.