[GSTG] Pull mirroring is sometimes unreliable - new mirrors frequently fail with "Network is unreachable"
Summary
The Pull mirroring QA test frequently fails on Staging because the mirroring attempts return the following error:
2:fetch remote: " connect to host staging.gitlab.com port 22: Network is unreachable\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n": exit status 128.
However, the same test will pass if run again a few minutes later. And then fail again later.
- Failing example: https://staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2022-02-14-11-17-24-a6329adeaa28825b/pull-mirror-target-project-0bf668f15f132dd1/-/settings/repository
- Passing example: https://staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2022-02-14-11-44-38-fef889fb513bf18b/pull-mirror-target-project-72ae744293ff6b82/-/settings/repository
The test performs the following steps:
- Create a project to mirror from (source project).
- Create a project to mirror to (target project).
- Configure the target project to pull from the source project, using SSH authentication.
- Copy the SSH key and add it as a deploy key in the source project.
- Update pull mirroring in the target project and wait for it to complete.
At first the mirroring status shows an error as Permission denied (publickey)
because the first mirroring attempt happens before the deploy key can be created. However that error should disappear when GitLab makes the next mirroring attempt.
Edited by Mark Lapierre