Hello,
I am currently upgrading GitLab from version 10.2.2-ee to 17.6.4-ee. I am performing manual upgrades and have reached version 16.0.10. Starting from this version, as soon as I upgrade to 16.3.X, I can no longer access certain projects; the web page remains in an infinite loading state. And if I upgrade to 16.7.X, I notice that the projects have lost volume (KiB) and are no longer accessible.
I cannot understand what the cause of the problem might be.
Since you’re using EE, I presume you’re a paid customer. Now that you’re at 16.x, you’re allowed to reach out for support (major version -2, so 15 and 16 are good for now, but once 18 comes out, 16 will be the minimum version available for support).
Assuming you’re doing this on a staging site, do your upgrade to 16.0.10 and then make sure all migrations are done:
If they’re all done and you move to 16.3.9 and you’re still seeing the infinite loading state, you’ll want to run a GitLabSOS and send it to support in a support ticket and describe the situation.
If you’re not doing this on a stage and your production instance is effectively borked, you should page an emergency.
Hope that helps!