Upgrade matrix to go from 14.5.2 to 15.0.0?

What is the upgrade matrix to go from 14.5.2 to 15.0.0?

Great question!

The upgrade path will be:

14.5.2 β†’ 14.9.4 β†’ 14.10.3 β†’ 15.0.0

Make sure to check for background migrations between upgrades and allow the migrations to complete before moving on to the next step in the upgrade path.

To play it safe, I always recommend taking a backup before upgrading a production system.

Best of luck - let us know how it goes!

1 Like

gitlab-greg, thanks for the quick response.
Different server.
What is the upgrade path to go from 13.2.6 to 15.0.0?

@gitlab-greg
Running handlers:
There was an error running gitlab-ctl reconfigure:

rails_migration[gitlab-rails] (gitlab::database_migrations line 51) had an error: Mixlib::ShellOut::ShellCommandFailed: bash[migrate gitlab-rails database] (/opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/resources/rails_migration.rb line 16) had an error: Mixlib::ShellOut::ShellCommandFailed: Command execution failed. STDOUT/STDERR suppressed for sensitive resource

I’m trying to go from 14.5.2 β†’ 14.6.0 β†’ 14.7.0 β†’ 14.8.0 β†’ 14.9.0 β†’ 14.9.4 β†’ 14.10.0 β†’ 14.10.3 β†’ 15.0.0. Is this the correct upgrade sequence?
I got as far as 14.9.4, but the database migration fails going from 14.9.4 β†’ 14.10.0.
I’m tempted to go back to the snap I had before starting, but that’s really tedious.
I’d rather try to fix it at this point.

What is the upgrade path to go from 13.2.6 to 15.0.0?

Anytime you need an upgrade path that is not found in our docs, you can use this tool that GitLab Support created: Upgrade Path

So for 13.2.6 β†’ 15.0.latest at this point in time, the upgrade path will be:

13.2.6 β†’ 13.12.15 β†’ 14.0.12 β†’ 14.9.5 β†’ 14.10.4 β†’ 15.0.2

To get from 14.5.2 to the latest version, the upgrade path will be:

14.5.2 β†’ 14.9.5 β†’ 14.10.4 β†’ 15.0.2

Note that:

  • when upgrading, it’s best to upgrade to the latest patch version for any minor version release. This is because major.minor.0 versions contain bugs and security flaws that get fixed in later patch releases
  • unless you absolutely need zero downtime upgrades, you do
    not need to upgrade each minor version. upgrading each minor version is only required for zero-downtime upgrades
  • there is no need or benefit to updating to major.minor.0 releases before moving on to a newer patch release for same major.minor version. For example, instead of:

14.5.2 β†’ 14.6.0 β†’ 14.7.0 β†’ 14.8.0 β†’ 14.9.0 β†’ 14.9.4 β†’ 14.10.0 β†’ 14.10.3 β†’ 15.0.0

it’d be much better, easier, (and less error prone) if you simply did:

14.5.2 β†’ 14.9.5 β†’ 14.10.4 β†’ 15.0.2

the database migration fails going from 14.9.4 β†’ 14.10.0.

Can you share the output of gitlab-rake db:migrate:status | grep -v up?

What error is the database migration failing with? (can usually be found in /var/log/gitlab/production.log or other GitLab logs)

1 Like

Thanks, I’m going to reset from a snap and try again following your guidance.

1 Like

@gitlab-greg
Greg,
I followed your recommendations and I was able to upgrade to 15.0.2 without any issues.

Thank you,
Stephen Palmer

2 Likes

@ergononsum that is wonderful news, thanks for the update! :tada: