Database Group Triage for week ending 2023-10-20

About

This issue is used by groupdatabase to triage issues and make sure they get properly assigned and prioritized. Each week, a bot will look up the old issue, pick the next assignee in the list, and submit a new issue with a list of any issues that may need attention from the team.

Last week's issue

Process

• Review any issues with undefined types
• Post any questions or pressing issues to the database group meeting doc
• Post a comment on the database group status issue

  For triage this week there were 0 issues in need of triage, 5 issues without throughput labels, and 5 other database issues reviewed. <link to this issue>

Bugs needing Severity

For each issue below:

1. For each typebug, spend up to 1 hour investigating or fixing the issue.
2. Assign it one of severity1, severity2, severity3, or severity4
3. Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and @rogerwoo to help with scheduling and priority.

• BackfillDraftStatusOnMergeRequests is not running properly on 14.1.8

Issues with Undefined Type

For each issue below:

1. Assess if the issue is appropriately assigned to groupdatabase, if not add the correct group label.
2. Add the proper work type label, or if the issue is a request for support, redirect the user to our support resources with the following message:

   Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including:
   * [Technical Support for Paid Tiers](https://about.gitlab.com/support/)
   * [Community Forum](https://forum.gitlab.com/)
   * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references)
   
   Please refer to our [Support page](https://about.gitlab.com/support/) for more information.
   
   If you believe this was closed in error, please feel free to re-open the issue.
   
   /label ~"support request"
   /close

3. If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
4. Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and @rogerwoo to help with scheduling and priority.

• Docs feedback: Clarify "upgrading … RDS … to a suitable version"
• Database Status Summary (Week ending - 2023-10-21)
• Add tooling to identify queries on partitioned tables that do not prune correctly
• Update SchemaCacheWithRenamedTable to be compatible with Rails 7.1
• Update ActiveRecord::GitlabPatches::Partitioning::Base to be compatible with Rails 7.1

Recent issues labeled database

For each issue below:

1. If the issue has no group label, consider if it should be addressed by groupdatabase and if so label it.
2. If the issue has a group, and you think they may need assistance from us:
   • If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
   • Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and/or @rogerwoo

• groupstatic analysis Sychronously create the index_vulnerability_occurrences_prim_iden_id_and_vuln_id index and remove it's predecessor
• groupcontainer registry Race condition finding or creating a container repository by path
• groupthreat insights VulnerabilityReads require index or indicies for all activity filter fields ( HasIssues, HasResolutiions, HasRemediations and HasMergeRequests )
• groupenvironments index_stopping_environments_on_updated_at synchronous database index addition
• groupsource code Create group approval rules via API

Customer Issue Hand-offs

For each issue below:

1. If the item already has a back and forth, check in with the @stomlinson to see if what needs to be handed off
2. Consider if it's right for our team and if not, ask the support rep to follow up with the correct team.
3. If the item is right for our team, spend some time accessing it and trying to assist.
4. If you need help, and the request seems pressing, ask in the team channel if there's someone who can help dig into it.

• Migration fails with "migrations_paths setting for ci database must be db/ci_migrate"~"Help group::Database", severity3
• The standby database is in a "running" state, but the standby leader itself is stuck in recovery~"Help group::Database"

@alexives if @dfrazao-gitlab isn't available this week, please reassign to @jon_jenkins cc @rogerwoo