Backport/fix ambiguous pipeline 17 9

What does this MR do and why?

Describe in detail what merge request is being backported and why

Backports this fix: !181334 (merged) Issue: #424158 (comment 2345303047)

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).

changed milestone to %17.9

assigned to @andrew.jung

marked this merge request as ready

added typebug label

added 1 commit

• 8bf92606 - Merge branch 'rcastro6-pipeline-configuration-fix' into 'master'

Compare with previous version

mentioned in issue #424158

@marc_shaw Could you look at this backport MR? (17.9)

Original MR: !181334 (merged) Context: #424158 (comment 2345303047)

requested review from @marc_shaw

@marc_shaw Could you look at this backport MR? (17.9)

Original MR: !181334 (merged) Context: #424158 (comment 2345303047)

added backend label

	2 Warnings
	You've made some app changes, but didn't add any tests. That's OK as long as you're refactoring existing code, but please consider adding any of the maintenancepipelines, maintenancerefactor, maintenanceworkflow, maintenanceperformance, documentation, QA labels.
	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.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@freinink (UTC-7, 2 hours behind author)	@hustewart (UTC-5, same timezone as 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

@andrew.jung, 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 Danger

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-omnibus: test report for 8bf92606

expand test summary

+---------------------------------------------------------------------+
|                           suites summary                            |
+----------------+--------+--------+---------+-------+-------+--------+
|                | passed | failed | skipped | flaky | total | result |
+----------------+--------+--------+---------+-------+-------+--------+
| Create         | 561    | 0      | 89      | 0     | 650   | ✅     |
| Plan           | 83     | 0      | 8       | 0     | 91    | ✅     |
| Govern         | 101    | 0      | 10      | 0     | 111   | ✅     |
| Verify         | 51     | 1      | 20      | 0     | 72    | ❌     |
| Package        | 30     | 0      | 14      | 0     | 44    | ✅     |
| Data Stores    | 45     | 1      | 11      | 1     | 57    | ❌     |
| Fulfillment    | 4      | 0      | 7       | 0     | 11    | ✅     |
| Monitor        | 12     | 0      | 13      | 0     | 25    | ✅     |
| Manage         | 26     | 0      | 20      | 0     | 46    | ✅     |
| Configure      | 1      | 0      | 3       | 0     | 4     | ✅     |
| Secure         | 6      | 0      | 3       | 0     | 9     | ✅     |
| Growth         | 0      | 0      | 2       | 0     | 2     | ➖     |
| ModelOps       | 0      | 0      | 1       | 0     | 1     | ➖     |
| GitLab Metrics | 2      | 0      | 1       | 0     | 3     | ✅     |
| Release        | 5      | 0      | 1       | 0     | 6     | ✅     |
| Systems        | 6      | 0      | 1       | 0     | 7     | ✅     |
| Analytics      | 3      | 0      | 0       | 0     | 3     | ✅     |
| Ai-powered     | 1      | 0      | 2       | 0     | 3     | ✅     |
+----------------+--------+--------+---------+-------+-------+--------+
| Total          | 937    | 2      | 206     | 1     | 1145  | ❌     |
+----------------+--------+--------+---------+-------+-------+--------+

e2e-test-on-gdk: test report for 8bf92606

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 135    | 0      | 23      | 0     | 158   | ✅     |
| Verify      | 51     | 0      | 21      | 0     | 72    | ✅     |
| Package     | 24     | 0      | 14      | 0     | 38    | ✅     |
| Plan        | 82     | 0      | 8       | 0     | 90    | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Govern      | 79     | 0      | 13      | 0     | 92    | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Secure      | 5      | 0      | 3       | 0     | 8     | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 427    | 0      | 129     | 0     | 556   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

@andrew.jung The e2e:test-on-omnibus-ee child pipeline has failed.

• e2e:test-on-omnibus-ee pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1677384323

e2e:test-on-omnibus-ee pipeline is allowed to fail due its flakiness. Failures should be investigated to guarantee this backport complies with the Quality standards.

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.

changed milestone to %17.10

added missed:17.9 label

changed milestone to %17.9

resolved all threads

resolved all threads

changed milestone to %17.10

changed milestone to %17.9

added severity3 label

marked the checklist item This MR has a [severity label] assigned (if applicable). as completed

marked the checklist item Ensure the e2e:test-on-omnibus-ee job has either succeeded or been approved by a Software Engineer in Test. as completed

@hustewart Are you able to give this a backend maintainer review for a backport? This one can be set MWPS as it's within our maintenance window for 17.9

requested review from @hustewart and removed review request for @marc_shaw

approved this merge request

added pipeline:mr-approved label

marked the checklist item This MR has been approved by a maintainer (only one approval is required). as completed

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels

@hustewart, 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.

resolved all threads

enabled automatic add to merge train when checks pass

removed pipeline:run-e2e-omnibus-once label

@andrew.jung The e2e:test-on-omnibus-ee child pipeline has failed.

• e2e:test-on-omnibus-ee pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1681370236

e2e:test-on-omnibus-ee pipeline is allowed to fail due its flakiness. Failures should be investigated to guarantee this backport complies with the Quality standards.

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.

Hey there , could you please make sure this merge request gets merged?

The merge request is set to auto-merge, but it is not currently mergeable (MR detailed_merge_status is discussions_not_resolved).

This message was generated automatically. Improve it or delete it.

resolved all threads

started a merge train

mentioned in commit 132f4532

merged