Error 500 on project home page when fork feature is enabled
Summary
It has been a few weeks I am getting an error 500 page on all Gitlab.com project homepage (and only the homepage) when the fork feature is enabled.
For example, I got it on https://gitlab.com/gitlab-org/gitlab (Request ID: 01H61E2NC2VR82RAT4C4R7AG9E) whereas I can access it without issue if I am not connected.
Steps to reproduce
I was able to determine that the issue may be linked to the fork feature been enabled (the default setting) by disabling it on one of my project and the error 500 left (for tracking I got the request ID: 01H61E6D9A5NNV88Q8PG29021E otherwise).
Implementation steps
Step | MR |
---|---|
1. GitLab version N.M: Add a NOT VALID foreign key constraint to the column to ensure GitLab doesn’t create inconsistent records. | !153402 (merged) |
2. GitLab version N.M: Add a data migration, to fix or clean up existing records. | !153101 |
3. GitLab version N.M+1: Validate the whole table by making the foreign key VALID. | ToBeImplemented |
Edited by Bojan Marjanovic