Unable to update gitlab-ee from 14.8.2

ajouve · January 13, 2023, 9:03am

Hi,

I am trying to update my gitlab ee version but I am stuck on 14.8.2

Running apt-get update and then apt-get install gitlab-ee I have

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
gitlab-ee is already the newest version (14.8.2-ee.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Then trying to force any version, for example apt-get install gitlab-ee=14.9.x-ee.0

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gitlab-ee is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '14.9.x-ee.0' for 'gitlab-ee' was not found

grove · January 13, 2023, 9:43am

What Linux distribution do you run on that host? It sounds like the problem you would run into if you were on a distribution that GitLab stopped supporting with 14.8.

ajouve · January 13, 2023, 9:58am

I am on 18.04

Ubuntu 18.04 LTS

  Linux ubuntu 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Should I update 22.04 ?

grove · January 13, 2023, 10:34am

Ubuntu 18.04 hasn’t reached EOL yet (but it will later this year), and there are packages of 15.7.3 for it on the official site.
So an upgrade shouldn’t be needed (but GitLab runs fine on newer Ubuntus, so you might want to consider it).
I assume you didn’t actually use a x in apt-get install gitlab-ee=14.9.x-ee.0, but tried various versions. Can you show us the actual output from some run?
Can you show us your /etc/apt/sources.list.d/gitlab<perhaps something I don't remember>?

ajouve · January 13, 2023, 11:19am

I have this message

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gitlab-ee is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '14.9.5-ee.0' for 'gitlab-ee' was not found

I have gitlab_gitlab-ee.list

# this file was generated by packages.gitlab.com for
# the repository at https://packages.gitlab.com/gitlab/gitlab-ee

# deb https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal
# deb-src https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal

gitlab_gitlab-ee.list.distUpgrade

# this file was generated by packages.gitlab.com for
# the repository at https://packages.gitlab.com/gitlab/gitlab-ee

# deb https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal
# deb-src https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal

gitlab_gitlab-ee.list.save

# this file was generated by packages.gitlab.com for
# the repository at https://packages.gitlab.com/gitlab/gitlab-ee

deb https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ bionic main
deb-src https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ bionic main

grove · January 13, 2023, 1:58pm

The first two of those files only contains comments, but the last looks correct.
I assume that you have run apt update (In most cases you can use apt in place of apt-get).
What does apt-cache policy gitlab-ee (apt has also implemented a lot of the functionality of apt-cache, but not policy) say? (It gives a few lines of output pr. version so be ready for quite a bit of output.)

ajouve · January 13, 2023, 4:04pm

I already did, apt and apt-get update, I tried again but it does not change anything

The result of apt-cache policy gitlab-ee is

gitlab-ee:
  Installed: 14.8.2-ee.0
  Candidate: 14.8.2-ee.0
  Version table:
 *** 14.8.2-ee.0 100
        100 /var/lib/dpkg/status

grove · January 16, 2023, 9:14am

Is that all that apt-cache policy says? It can’t even find 14.8.2 anywhere (except locally - because it is installed).

Can you share the output of apt update?

ajouve · February 4, 2023, 10:16am

The full apt-cache policy is

Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 https://packages.gitlab.com/runner/gitlab-runner/ubuntu jammy/main amd64 Packages
     release v=1,o=packages.gitlab.com/runner/gitlab-runner,a=jammy,n=jammy,l=gitlab-runner,c=main,b=amd64
     origin packages.gitlab.com
 500 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=amd64
     origin security.ubuntu.com
 100 http://ubuntu.mirrors.ovh.net/ubuntu jammy-backports/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin ubuntu.mirrors.ovh.net
 100 http://ubuntu.mirrors.ovh.net/ubuntu jammy-backports/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=main,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy-updates/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy-updates/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy-updates/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy-updates/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy/multiverse amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy/universe amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy/restricted amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=amd64
     origin ubuntu.mirrors.ovh.net
 500 http://ubuntu.mirrors.ovh.net/ubuntu jammy/main amd64 Packages
     release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=amd64
     origin ubuntu.mirrors.ovh.net
Pinned packages:

apt-cache policy gitlab-ee return

gitlab-ee:
  Installed: 14.8.2-ee.0
  Candidate: 14.8.2-ee.0
  Version table:
 *** 14.8.2-ee.0 100
        100 /var/lib/dpkg/status

apt update returns

Get:1 http://ubuntu.mirrors.ovh.net/ubuntu jammy InRelease [270 kB]
Get:2 http://ubuntu.mirrors.ovh.net/ubuntu jammy-updates InRelease [114 kB]
Get:3 http://ubuntu.mirrors.ovh.net/ubuntu jammy-backports InRelease [107 kB]
Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:5 https://packages.gitlab.com/runner/gitlab-runner/ubuntu jammy InRelease
Fetched 601 kB in 1s (464 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

grove · February 16, 2023, 10:07am

Sorry, I didn’t see your reply before now.

It seems you’ve spend the time upgrading to jammy, that’s probably a good idea.

What I notice now is that apt update only mentions the repo for the gitlab-runner, but not for gitlab itself. What did you do related to gitlab when you upgraded? You should have a file like the gitlab_gitlab-ee.list you show above where the two last lines are not comments, and have jammy instead of focal (although the focal packages work fine on jammy at the moment).

ajouve · February 16, 2023, 11:29am

Hi,
Thanks for the update

I had this issue before upgrading so I tried to upgrade and it does not solved the issue

in /etc/apt/sources.list.d/gitlab_gitlab-ee.list I have

# this file was generated by packages.gitlab.com for
# the repository at https://packages.gitlab.com/gitlab/gitlab-ee

# deb https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal
# deb-src https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ focal main # disabled on upgrade to focal

I only have commented lines in this file

grove · February 16, 2023, 11:50am

First of all, from

you should install GitLab Runner on a machine that’s separate from the one that hosts the GitLab instance

If you haven’t done anything related to the gitlab-repos, I wouldn’t expect an upgrade to fix your issue, but it might make it a little easier to debug, and it gives you four more years before you have to upgrade the OS again.

My suggestion would be to edit that file as described (and also remove the comments saying # disabled on upgrade to focal), and delete all other files mentioning gitlab(-ee) from /etc/apt/sources.list.d.

ajouve · February 16, 2023, 7:50pm

It worked, thanks

I had to set focal back to upgrade v14 due to the upgrade path, then v15 worked with jammy