Adding a deploy key to every project repository breaks the UI display of deploy keys: "Error getting deploy keys"

Summary

Project UIs fail to render, returning a 500 and "Error getting deploy keys".

Steps to reproduce

Through automation, we create a deploy key if not present for every Gitlab project in our self-managed instance. We have 81,175 projects today.

APIs are still functional, we can list/create, but UI driven interactions are not available:

Example Project

We're a self-managed instance, I can discuss privately more about our instance/usage.

What is the current bug behavior?

A get request is fired to /namespace/project/-/deploy_keys and returns 500 after almost exactly 1 minute

What is the expected correct behavior?

Loading deploy keys UI

This issue was automatically tagged with the label ~"group::release" by TanukiStan, a machine learning classification model, with a probability of 0.88.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can use the @gitlab-bot label ~"group::<correct group name>" command, or leave the issue to be triaged by group leaders initially assigned by TanukiStan.

This message was generated automatically. You're welcome to improve it.

added automation:ml label

Hey @connelldave, thank you for creating this issue!

To get the right eyes on your issue more quickly, we encourage you to follow the issue triage best practices.

PLEASE NOTE: You will need to use the @gitlab-bot label command to apply labels to this issue.

To set expectations, GitLab product managers or team members can't make any promise if they will proceed with this. However, we believe everyone can contribute, and welcome you to work on this proposed change, feature or bug fix. There is a bias for action, so you don't need to wait. Try and spin up that merge request yourself.

If you need help doing so, we're always open to mentor you to drive this change.

This message was generated automatically. You're welcome to improve it.

added automation:self-triage-encouraged label

Large GitLab Premium customer is affected by this bug: ZD(internal)

Despite the implementation of pagination, this bug remains reproducible in GitLab version 16.8.2. It appears that the following issue aims to add an index to improve performance.

• #433275

Hi @nagyv-gitlab , one of our large premium customers is still encountering this bug. Just wondering if there is any chance we could prioritize resolving this issue?

Hi @nagyv-gitlab, in #433275 (comment 1798536316) we noticed that the absence of index results in the performance problems resulting in 500 errors in the UI while accessing the deploy keys.

One of our large customer is affected by this issue. Just wondering if there is any chance we could prioritize resolving this issue? any approximate timeline would be very helpful

added customer label

added bugperformance devopsdeploy groupenvironments typebug labels

added sectioncd label

mentioned in issue gitlab-org/quality/triage-reports#16726 (closed)

mentioned in issue gitlab-org/quality/triage-reports#16806 (closed)

marked this issue as a duplicate of #444958

closed

marked this issue as related to #444958

mentioned in issue #444958