Commit 62cb2150 authored by Leigh Stoller's avatar Leigh Stoller

Hmm, I never added the cancellation code (from the old start code) to

the new os_setup path in StartSliver(). This was causing a variety of
annoying emails to the tbops lists cause DeleteSliver and StartSliver()
not doing the proper cancel dance.
parent 1d172315
......@@ -1387,6 +1387,27 @@ sub ActionStart($$;$)
print STDERR "os_setup exited with status $rval\n";
}
#
# Check for cancelation. We skip all the logging and email.
#
if ($experiment->Canceled()) {
print STDERR "ActionStart canceled; terminating early!\n";
# Mark all thee nodes as canceled (which really means failure).
foreach my $node (values(%nodes)) {
$node->_sliver()->SetStatus("canceled")
if (defined($node->_sliver()));
}
# Reset before return; do not want it left.
$slice->LockTables();
# Do this first so others know we are reacting to the cancel.
$slice->ClearMonitorPid();
$experiment->SetCancelFlag(0);
$slice->UnLockTables();
$msg = "canceled; terminating early";
goto bad;
}
#
# See what nodes succeeded or failed. We want to hold off setting
# the new state on the slivers until the end so that we do not flip
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment