Monday 2024-05-27 09:14 UTC - `gitlab-org/gitlab` broken `master` with rspec integration pg14 2/16

gitlab-org/gitlab pipeline #1306696418 failed

Pipeline ID	Branch	Commit	Merge request	Source	Duration	Triggered by
1306696418	master	Merge branch 'add-sharding-key-tracking-issues-value_stream_management' into 'master'	Add sharding key tracking issues for value_stream_management	push	66.61 minutes	Adam Hegyi

Failed jobs (1):

• rspec integration pg14 2/16 Job ID: 6946213436 (retry with @gitlab-bot retry_job 6946213436)

Attribution:

• groupcontainer registry Category:Container Registry ./spec/requests/api/graphql/container_repository/container_repository_details_spec.rb[1:8:1]
• groupcontainer registry Category:Container Registry ./spec/requests/api/graphql/container_repository/container_repository_details_spec.rb[1:8:2:1]
• groupcontainer registry Category:Container Registry ./spec/requests/api/graphql/container_repository/container_repository_details_spec.rb[1:11:1:1]

This incident is attributed to groupcontainer registry and posted in #g_container-registry.

How to close this incident

• Follow the steps in the Broken master handbook guide to
  • escalate
  • triage, and
  • resolve
• Reminder: apply the appropriate ~master-broken:* label to document root cause before closing the incident.

Quick Tips:

• you can retry all failing jobs with @gitlab-bot retry_pipeline 1306696418.
• a message can be posted in #backend_maintainers or #frontend_maintainers to get a maintainer take a look at the fix ASAP.
• add the pipeline:expedite label, and master:broken or master:foss-broken label, to speed up the master-fixing pipelines.