E2E test: Fork can be created after moving parent project to a new Gitaly storage
The test should confirm that a new fork can be created after moving the parent project is moved a new Gitaly shard/storage.
See gitlab-org/gitlab#38264 (closed) and gitlab-org/gitlab!21339 (comment 256175138)
Tasks
-
Add a new gitlab-qa
scenario with a secondary Gitaly storage: gitlab-org/gitlab-qa!347 (merged) -
Add the new test case: gitlab-org/gitlab!21383 (merged) -
Add the scenario to the nightly pipeline. https://gitlab.com/gitlab-org/quality/nightly/-/merge_requests/51
- [ ] Add the scenario to pipeline-common.It's an orchestrated test so can't be run on static environments -
Add the scenario to the gitlab-qa pipeline.
Test steps
- create public repo
- create fork
- move public repo to different gitaly storage
- wait for move to complete?
- create second fork (there should not be a 500 error)
- push to fork to confirm?
Edited by Mark Lapierre