Fix background jobs that previously failed and were never completed properly#3113
Draft
Fix background jobs that previously failed and were never completed properly#3113
Conversation
Some background jobs previously failed and did not have success or finished fields set due to bugs. This migration targets those jobs to update these fields so that the existing API endpoints for retrying background jobs can be used.
This is preferable to simply retrying older failed replication background jobs, as it's possible that the objects they correlate to have been deleted or changed since and so those old background jobs would no longer be applicable.
tw4l
force-pushed
the
issue-3067-rerun-bg-jobs-not-finished
branch
from
6277866 to
0bf8c12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3067
This PR includes two migrations:
finishedorsuccessset properly in the databaseWork in progress. The migration numbers may need to be modified depending on relative merge timing of this PR, #3111, and #3112