Closed
Bug 1315670
Opened 9 years ago
Closed 9 years ago
ATMO V2: reset last run time when changing a job schedule
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Assigned: mdoglio)
References
Details
Attachments
(1 file)
The job scheduler logic is based on the job last run time. There could be a case where the job ran 5 minutes before it's changed and it won't run until the next hour/day/week. From the user perspective this is unexpected at least, we should reset the last run time whenever a job schedule is modified.
|
||
Comment 1•9 years ago
|
||
|
Assignee | |
Comment 2•9 years ago
|
||
This is now on master
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•