CODEWITHSUNDEEP
gitrepositorygitlab
sadmicrowave
sadmicrowave

Reputation: 40962

gitlab 6.0 Lost Project After Upgrade

After upgrading from Gitlab v5.4 to v6.0 I have completely lost a project that has been active used and pushed to for 5 months. I performed a backup prior to the upgrade, I just can't find anything about restoring missing projects after an upgrade. Can someone help?

Here is an excerpt to show that everything is up-and-running:

:/home/git/gitlab$ sudo service gitlab start
The Unicorn web server already running with pid 29977, not restarting.
The Sidekiq job dispatcher is already running with pid 29998, not restarting
The GitLab Unicorn webserver with pid 29977 is running.
The GitLab Sidekiq job dispatcher with pid 29998 is running.
GitLab and all it's components are up and running.

The problem is only related to the most recent project that has been created. I still have the others prior to this newest one that is missing.

Upvotes: 1

Views: 899

Answers (3)

sadmicrowave
sadmicrowave

Reputation: 40962

Figured it out! Its because of the namespaces. For some reason the groups/namespaces did not get activated when I did the upgrade. Therefore, the projects that were previously associated with those namespaces did not get presented on the main page. Once I reactivated the namespaces (app-development, and web-development) and assigned the missing project to one of those, everything works again... phew that was very close!

By the way, something like this is covered at the end of the upgrade docs in gitlab: https://github.com/gitlabhq/gitlabhq/blob/master/doc/update/5.4-to-6.0.md

Upvotes: 0

Ash Wilson
Ash Wilson

Reputation: 24478

You can restore backups with rake:

rake gitlab:backup:restore

However, GitLab does a check to ensure that you can only restore when you're on the same version (actually, by commit hash), so you'd have to downgrade GitLab first.

Was your project in the root namespace? GitLab 6.0 did away with the concept of a root namespace, so it's possible that your project was lost when you ran migrate_global_projects, especially if the project's owner had a project in his or her namespace with the same name. You could fix this by rolling back the upgrade, restoring from backup, and manually moving the project to a non-global namespace.

Upvotes: 2

Kyle Kelley
Kyle Kelley

Reputation: 14144

Though it won't have all your issue and merge request history, you could make a new project and just push it back up to your GitLab instance.

Upvotes: 0

Related Questions