Troubleshoot backport failures #329
Open
Conversation
This file contains 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
Lately we see a lot of backport workflows fail. The pattern always
seems to be that the first backport (to branch/v17) succeeds, but
subsequent backports (to v15 and v16) almost always fail.
The failure looks to be a GitHub-specific failure, not a generic git
failure:
remote: fatal error in commit_refs
To https://github.com/gravitational/teleport
! [remote rejected] bot/backport-51989-branch/v15 > bot/backport-51989-branch/v15 (failure)
error: failed to push some refs to https://github.com/gravitational/teleport
To aid in troubleshooting we:
1. Temporarily reverse the order of branches. This will tell us if it's
always the first branch that succeeds, or if it's always branch/v17
that succeeds.
2. Add the --verbose flag to the git push command in case we get any
more debug info.
doggydogworld
approved these changes
Feb 11, 2025
rosstimothy
approved these changes
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Lately we see a lot of backport workflows fail. The pattern always seems to be that the first backport (to branch/v17) succeeds, but subsequent backports (to v15 and v16) almost always fail.
The failure looks to be a GitHub-specific failure, not a generic git failure:
To aid in troubleshooting we: