Database Group Triage for week ending 2023-10-06

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, 2 issues without throughput labels, and 10 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.

• After upgrading to gitlab-ce 16.4.1 reconfigure fails
• Schema Validations: Incorrect reports for boolean columns
• DB-Migration failure during GitLab-Upgrade from 16.3.4 to 16.4.0

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.

• single codebase
• Update verbiage on Upgrade Path tool

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

• groupgeo Geo - Remove project_repository_states table
• groupgeo Geo - Remove ignored legacy project repositories columns from geo_node_statuses table
• groupgeo Geo - Remove ignored legacy wiki repositories columns from geo_node_statuses table
• groupgeo Geo - Remove unused project_registry table
• groupacquisition Create migration to drop ignored database column campaign in in_product_marketing_email
• groupthreat insights index_vulnerabilities_on_project_id_and_id synchronous database index addition
• groupthreat insights Backend: Add hasMergeRequest to Severities Count
• groupthreat insights Drop tmp_index_vulnerability_occurrences_uuid_cast index
• groupsecurity policies Remove security policy configuration bot_user_id column
• groupdistribution A few possible optimizations for pg_upgrade

Customer Issue Hand-offs

For each issue below:

1. If the item already has a back and forth, check in with the @mattkasa 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.

• CPU spike with one query running frequently - debug index difference~"Help group::Database"

@alexives if @praba.m7n isn't available this week, please reassign to @stomlinson cc @rogerwoo