Make mirroring failures visible to maintainers

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Feature request

Surface mirroring failures to project maintainers so they can be quickly resolved

Problem

GitLab deployments and releases depend on mirroring between the Canonical and Security repositories, and between the Ops and Dev instances. Recently we've had a number of mirroring failures that have affected deployments and releases but have gone unnoticed until someone happens to see them. Having both the mirroring configuration and errors visible only in the Settings area is making it harder for people to notice failures.

Examples:

1. Release tag missing - During the preparation for the 15.7 release we tagged the release and had success statuses. Only later did we see that mirroring had somehow failed and tags were missing. A retry fixed the problem. Discussion thread where the problem is discovered and fixed - internal.

Events timeline:

• 2022-12-21 12:05 UTC - 15.7 is tagged -https://gitlab.slack.com/archives/C0139MAV672/p1671624304452499
• 2022-12-21 12:11 UTC - CE and EE tags are pushed to the dev repo - https://gitlab.slack.com/archives/C0139MAV672/p1671624717712019 Example pipeline https://dev.gitlab.org/gitlab/omnibus-gitlab/-/tags/15.7.0+ee.0
• 2022-12-21 12:12 UTC - charts tag is pushed https://gitlab.slack.com/archives/C0139MAV672/p1671624737563209 but the didn't get created until manual job retries on https://dev.gitlab.org/gitlab/charts/components/images/-/pipelines/265890

2. PAT changes broke the mirroring used to create deployment QA issues - For compliance reasons we track package contents and testing for each deployment. These issues stopped being created and it took some time for us to discover that the reason was because of mirroring failures linked to PAT changes. gitlab-com/gl-infra/delivery#2609 (closed)