[16.10] Backport handle null owner when indexing projects
What does this MR do and why?
Backport !147951 (merged) to %16.10
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:package-and-test-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 %16.10
added groupglobal search typebug labels
assigned to @terrichu
added devopsdata stores sectioncore platform labels
- A deleted user
added backend label
1 Warning The e2e:package-and-test-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:package-and-test-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 @praba.m7n
(UTC+2, 6 hours ahead of author)
@mhamda
(UTC+2, 6 hours ahead of author)
Please check reviewer's status!
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:package-and-test-ee
@terrichu, the
package-and-test
job must complete before merging this merge request.*If there are failures on the
package-and-test
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 severity3 label and removed backend devopsdata stores sectioncore platform labels
added devopsdata stores sectioncore platform labels
@sdungerwal would you mind a backend maintainer review and merge for the backport?
requested review from @sdungarwal
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-package-and-test:
test report for 79f2bc5cexpand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | Govern | 269 | 0 | 19 | 1 | 288 | ✅ | | Fulfillment | 8 | 0 | 75 | 1 | 83 | ✅ | | Plan | 245 | 0 | 19 | 0 | 264 | ✅ | | Create | 554 | 0 | 80 | 8 | 634 | ✅ | | Verify | 147 | 0 | 30 | 3 | 177 | ✅ | | Package | 205 | 0 | 37 | 18 | 242 | ✅ | | Data Stores | 117 | 0 | 28 | 0 | 145 | ✅ | | Systems | 10 | 0 | 0 | 0 | 10 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Analytics | 7 | 0 | 0 | 0 | 7 | ✅ | | Release | 15 | 0 | 3 | 0 | 18 | ✅ | | Monitor | 32 | 0 | 13 | 0 | 45 | ✅ | | Manage | 39 | 0 | 11 | 1 | 50 | ✅ | | Configure | 1 | 0 | 9 | 0 | 10 | ✅ | | Secure | 6 | 0 | 3 | 0 | 9 | ✅ | | Ai-powered | 0 | 0 | 3 | 0 | 3 | ➖ | | Growth | 0 | 0 | 6 | 0 | 6 | ➖ | | ModelOps | 0 | 0 | 3 | 0 | 3 | ➖ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 1657 | 0 | 340 | 32 | 1997 | ✅ | +----------------+--------+--------+---------+-------+-------+--------+
- A deleted user
added backend label
- Resolved by Siddharth Dungarwal
@terrichu Thee2e:package-and-test-ee
job has failed.-
e2e:package-and-test-ee
pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1237553073
e2e:package-and-test-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 %16.11
added missed:16.10 label
- Resolved by Siddharth Dungarwal
@sdungarwal
, thanks for approving this merge request.This is the first time the merge request has been approved. Please ensure the
e2e:package-and-test-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.
enabled an automatic merge when the pipeline for cdbe15f2 succeeds
- Resolved by Siddharth Dungarwal
@terrichu Thee2e:package-and-test-ee
job has failed.-
e2e:package-and-test-ee
pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1238216646
e2e:package-and-test-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. -
mentioned in commit d9d8117e
mentioned in incident gitlab-org/release/tasks#9945 (closed)
@terrichu Thee2e:package-and-test-ee
job has failed.-
e2e:package-and-test-ee
pipeline: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1238794234
e2e:package-and-test-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.-