"No repository The repository for this project does not exist. This means you can not push code until you create an empty repository or import existing one."

How to Use GitLab Upgrade
1

After gitlab-ce upgrade from version 12.2.0 to 15.10 in some repositories i am seeing below error.

" No repository

The repository for this project does not exist.
This means you can not push code until you create an empty repository or import existing one."

2

How did you do the upgrade? Did you follow the Gitlab documentation and the upgrade path? Since direct upgrade from 12.2.0 to 15.10 is not supported and will break your installation.

If you did direct upgrade, I suggest restore your server from your backup - hopefully you have one?

3

I followed this upgrade path “Upgrade Path”.

4

This problem is with only some repositores, not all .

5

Not sure what that link is, I prefer to follow the official Gitlab docs here: Upgrading GitLab | GitLab

And did you wait for background migrations to finish before starting the next upgrade on the upgrade path? Or as soon as the upgrade finished, you started the next one?

6

I started the next upgrade immediately.

7

Right, so you’ll have to go into the Admin section on your Gitlab then monitoring and background migrations. You can also do:

gitlab-rake db:migrate:status

to check if they are all OK or not. I expect your problems are because you didn’t wait for background migrations to complete, and this sounds like the reason why your install broke. Whether you can recover this now, might not be so simple. Probably easier to restore back to 12.2.0 and then follow the Gitlab documentation properly.

8

I can see that there are some no data.

Also noticed all the repositories data missing is from users who were blocked by the admin.

9

My guess is some of your repos didn’t switch successfully to hashed storage. As others have suggested, check your background migrations; you may see the repos shown as failing to migrate.

1 Like
10

Yes, some time around the mid 13.x there was a known problem where repos would be missed for an obscure edge case. GitLab Support have a snippet to look for and correct these

There are also quite a few long-running background migrations, and batched background migrations (introduced in late 14.x early 15.x). Generally you must ensure migrations have completed before moving along to the next minor version (yellow warning button on the Support tool that OP linked).

There’s also a switch from Unicorn to Puma, deprecation of NFS storage and move to Gitaly

1 Like