Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading from 14.0.0 to 14.8.2 getting error of data migration #2850

Open
Swati-Gawali opened this issue Nov 3, 2023 · 4 comments
Open

Comments

@Swati-Gawali
Copy link

Upgrading from 14.0.0 to 14.8.2 getting error of data migration with the upgrade path 14.0.0 > 14.0.6 > 14.1.1 > 14.3.1 > 14.5.2 > 14.6.2 > 14.8.2.

While Upgrading from 14.1.1 to 14.3.2/ or any other version after that showing the below error.

image

Please look into it and share any feedback if one is having solution for this.

@kkimurak
Copy link
Contributor

kkimurak commented Nov 3, 2023

As you can see in the error message, there are some unfinished migration. You have to run specific version of gitlab for a while. It is said that

Some installations may need to run GitLab 14.0 for at least a day to complete the database changes introduced by that upgrade.

See documents about Background migration. You may also want to refer GitLab 14 changes.


Some tips to get suitable answers:

  1. Paste messages as text (prefer to use fenced code block), not image. It is a consideration for respondents to make it easier to investigate the question.
  2. Search the error message before you create new issue. You can find out some similar issues by searching by the word "background migration" in the error message shown in image you submit.

I'm sorry if I'm wrong but you are using official gitlab image gitlab-ce or gitlab-ee, right? gitlab-rake (shown in error message) is a special command only available for omnibus-based gitlab, not for sameersbn/gitlab, an unofficial image developped here.
Then this issue is, (yes it's true that the question is about gitlab, but it's fair to say that it's) mostly off-topic - you are in wrong place to post your issue. Please ask on GitLab codebase.
I wouldn't go so far as to say that off-topic questions are extremely problematic, but you're less likely to get the right answer.

@gjrtimmer
Copy link
Contributor

gjrtimmer commented Nov 28, 2023

I hope this helps. Your upgrade jump is too large. GitLab documentation clearly states the required upgrade path for your version:

For your version it should be: GitLab 14: 14.0.12 > 14.3.6 >
14.9.5 > 14.10.5.

I advise you to read the documentation, and use your backup to perform the right upgrade path. After you are on 14.10.5 you can make the jump to 15. Then follow the upgrade requirements in the first link of this post to continue your upgrade. Here is a copy of the text from the above link.

Find where your version sits in the upgrade path:

  • GitLab 14: 14.0.12 > 14.3.6 > 14.9.5 > 14.10.5.
  • GitLab 15: 15.0.5 > 15.1.6 (for GitLab instances with multiple web nodes) > 15.4.6 > 15.11.13.
  • GitLab 16: 16.0.x (only instances with lots of users or large pipeline variables history) > 16.1(instances with NPM packages in their Package Registry) > 16.2.x (only instances with large pipeline variables history) > 16.3 > latest 16.Y.Z.Find where your version sits in the upgrade path:

GitLab 14: 14.0.12 > 14.3.6 >
14.9.5 > 14.10.5.
GitLab 15: 15.0.5 > 15.1.6 (for
GitLab instances with multiple web nodes) > 15.4.6 >
15.11.13.
GitLab 16: 16.0.x (only
instances with lots of users or
large pipeline variables history) >
16.1(instances with NPM packages in their Package Registry) >
16.2.x (only instances with large pipeline variables history) >
16.3 > latest 16.Y.Z.

@alexislefebvre
Copy link
Contributor

alexislefebvre commented Dec 8, 2023

@gjrtimmer This answer is valid but none of the links work: the first one redirect to a login page, the others lead to “Not found” pages.

Here is the official doc with links that work: https://docs.gitlab.com/ee/update/#upgrade-paths

@gjrtimmer
Copy link
Contributor

Sorry about that, it came from the help of my private instance. THe link of @alexislefebvre is the correct one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants