Bridge allows to start job decisions before they are properly canceled by Native Scheduler
After canceling a job decision Bridge soon returns a new job page with a proper status. In addition, users can immediately start a job decision again. But the previous job decision wasn't likely canceled by Native Scheduler since it needs some time. So, such sequence of actions result in strange consequences.
#3 Updated by Vladimir Gratinskiy about 1 year ago
- % Done changed from 0 to 100
- Status changed from New to Resolved
- Due date set to 12/18/2017
I've added new status "Cancelling" which will be set for jobs after pressing button "Cancel decision" until scheduler confirm that job is cancelled. It should be done in request "get_jobs_and_tasks". As before in field
data["jobs"]["cancelled"] there will be cancelled jobs' identifiers. But scheduler should add identifiers of cancelled (confirmed that cancelled) jobs here. And "Cancelling" jobs would become "Cancelled" after this. These cahnges are done in branch "fix_8632" together with #8632 and #8626.