Bug #8384
closedBridge allows to start job decisions before they are properly canceled by Native Scheduler
100%
Description
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.
Updated by Ilja Zakharov over 7 years ago
I suggest either do not send status pending until the scheduler confirms that it have cancelled the job or block starting solution buttons for a user waiting for the same confirmation from the scheduler.
Updated by Evgeny Novikov about 7 years ago
- Priority changed from High to Urgent
- Target version set to 2.0
Indeed this issue can cause restarting Native Scheduler assuming that all properly solving jobs to be terminated. So, let's avoid these races as soon as possible.
Updated by Vladimir Gratinskiy about 7 years ago
- Due date set to 12/18/2017
- Status changed from New to Resolved
- % Done changed from 0 to 100
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.
Updated by Evgeny Novikov almost 7 years ago
- Target version changed from 2.0 to 1.0
As far as we postpone Klever version:0.3, let's include this issue there.
Updated by Ilja Zakharov almost 7 years ago
- Status changed from Resolved to Verified
Added support to the scheduler and verified.
Updated by Ilja Zakharov almost 7 years ago
- Status changed from Verified to Closed