Omnibus upgrade from 12.10.6 to 13.0.6

How to Use GitLab Upgrade
1

First time upgrading a major version of Omnibus Gitlab and I’m wondering if it is a simple as running the upgrade. Can I go directly from 12.10.6 to 13.0.6? I understand that there is a move to puma from unicorn. We have always used the default unicorn settings and are likely to do the same with the puma setting initially. The

Wondering if there are any other things I might need to take into consideration?

Thanks

apt list --upgradeable
gitlab-ce/bionic 13.0.6-ce.0 amd64 [upgradable from: 12.10.6-ce.0]

gitlab-rake gitlab:env:info

System information
System: Ubuntu 18.04
Current User: git
Using RVM: no
Ruby Version: 2.6.5p114
Gem Version: 2.7.10
Bundler Version:1.17.3
Rake Version: 12.3.3
Redis Version: 5.0.7
Git Version: 2.26.2
Sidekiq Version:5.2.7
Go Version: unknown

GitLab information
Version: 12.10.6
Revision: 833223f2a7f
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 11.7
URL: http://ncti105.seqldn.com
HTTP Clone URL: http://ncti105.seqldn.com/some-group/some-project.git
SSH Clone URL: git@ncti105.seqldn.com:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version: 12.2.0
Repository storage paths:

  • default: /data1/git-data/repositories
    GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
    Git: /opt/gitlab/embedded/bin/git
2

The major thing to be aware of with upgrading from 12 to 13, is that PostgreSQL versions below 11 are no longer supported, and until late in the 12 cycle the default was 10.. But the output you’ve provided shows that you’re already on 11.7.

If you used the default configuration for unicorn, there shouldn’t be anything to worry about in regards to the switch to puma.

I think the upgrade you’re talking about should be supported.

3

Hi,

in order to stay safe, I recommend to upgrade to the latest 12.10.x version, and then upgrade to 13.x. This ensures that all migrations are done prior the major upgrade.

In terms of the switch from Unicorn to Puma, verify that you’re not using a custom http port for instance (e.g. behind a custom proxy). There’s upgrading docs which should help in case.

Cheers,
Michael