Note about issues with storage migration
What does this MR do?
GitLab 13.4.0 includes a background migration to move repositories from legacy storage to hashed storage. This migration has known issues that result in what appears to be lost repositories. The problem is recoverable, but the customer experience is exceptionally negative. There is a fix to prevent the problem, but the fix is only backported to 13.5.4 (and committed to 13.6 natively). Since we are now working on 13.10, it's unlikely we would backport this fix to 13.4, but a number of customers have run into this problem over the past few weeks. Documenting the issue here seems to be the most useful place to note the problem and help customers avoid it.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team