Fix broken merge train merge when target branch deleted
What does this MR do and why?
This is a backport of !165216 (merged), part of a series of fixes we've done related to merge trains getting stuck. The backport is for a critical-customer-escalation #500887 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:test-on-omnibus-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Merge request reports
Activity
changed milestone to %17.4
added devopsverify grouppipeline execution priority2 sectionci severity2 typebug labels
assigned to @hfyngvason
added pipelinetier-1 label
requested review from @mfanGitLab
- A deleted user
added backend label
3 Warnings There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add
the feature flagexists. Otherwise, if you think the changes here don't need
to be under a feature flag, please add the label feature flagskipped, and
add a short comment about why we skipped the feature flag.For guidance on when to use a feature flag, please see the documentation.
Backporting to older releases requires an exception request process The e2e:test-on-omnibus-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:test-on-omnibus-ee" section for more details.Reviewer roulette
Category Reviewer Maintainer backend @olaoluro
(UTC+0, 5 hours ahead of author)
@seanarnold
(UTC+13, 18 hours ahead of author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
QA
e2e:test-on-omnibus-ee
@hfyngvason, the
e2e:test-on-omnibus
job must complete before merging this merge request.*If there are failures on the
e2e:test-on-omnibus
pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the#test-platform
Slack channel.If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangeradded pipeline:mr-approved label
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
- Resolved by Jenny Kim
@mfanGitLab
, thanks for approving this merge request.This is the first time the merge request has been approved. Please ensure the
e2e:test-on-omnibus-ee
job has succeeded. If there is a failure, a Software Engineer in Test (SET) needs to confirm the failures are unrelated to the merge request. If there's no SET assigned to this team, ask for assistance on the#test-platform
Slack channel.
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-omnibus:
test report for d88a8a2bexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 20 | 0 | 0 | 0 | 20 | ✅ | | Govern | 20 | 0 | 0 | 0 | 20 | ✅ | | Plan | 28 | 0 | 0 | 0 | 28 | ✅ | | Package | 0 | 0 | 4 | 0 | 4 | ➖ | | Verify | 4 | 0 | 0 | 0 | 4 | ✅ | | Data Stores | 4 | 0 | 0 | 0 | 4 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 76 | 0 | 4 | 0 | 80 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-gdk:
test report for d88a8a2bexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 5 | 0 | 0 | 0 | 5 | ✅ | | Govern | 4 | 0 | 0 | 0 | 4 | ✅ | | Data Stores | 1 | 0 | 0 | 0 | 1 | ✅ | | Plan | 6 | 0 | 0 | 0 | 6 | ✅ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Verify | 1 | 0 | 0 | 0 | 1 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 17 | 0 | 1 | 0 | 18 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
removed pipeline:run-e2e-omnibus-once label
changed milestone to %17.6
added missed:17.4 label
changed milestone to %17.4
added this merge request to the merge train at position 2
mentioned in commit 9095ca0c
mentioned in issue #500887 (closed)