Gitlab Self Managed Instance Upgrade 13.10.0

I am not able to install the latest version of GitLab 13.10.0 using the following command. It’s only installing until 13.9.4.
sudo EXTERNAL_URL=“https://gitlab.example.com” zypper install gitlab-ee

Below is the message I am getting when I try to run install again using the command above from 13.9.4.

“There is an update candidate for ‘gitlab-ee’, but it is from a different vendor. Use ‘zypper install gitlab-ee-13.10.0-ee.0.sles12.x86_64’ to install this candidate.”

I also ran “sudo zypper update” hoping it might help. But still it was giving the same message as given above.

Do you know why it’s saying “coming from a different vendor”? Why it’s saying to use a different command and how can I resolve it?

Appreciate your help!

Hi @akaiserk , thanks for posting this.

I’ve not heard of this issue before but I can confirm that we built and released official rpm packages for gitlab-ee-13.10.0-ee.0.sles12.x86_64 four days ago. The “from a different vendor” has me curious if something happened to the repo source or GPG key.

Can you re-do the “quick install” one-liner, try to upgrade to 13.10.0 again, and verify whether the problem persists?

Hi gitlab-greg,

Good Morning. Thank you for your response. I tried the on-liner and doing the re-install again. Below are the outputs for curl and install. It’s still the same behavior.

  1. Below is the console output for the one-liner curl

output:
curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.rpm.sh | sudo bash
Detected operating system as sles/12.5.
Checking for curl…
Detected curl…
Downloading repository file: https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/config_file.repo?os=sles&dist=12.5&source=script
done.
Repository ‘gitlab_gitlab-ee’ is up to date.
Specified repositories have been refreshed.
Repository ‘gitlab_gitlab-ee-source’ is up to date.
Specified repositories have been refreshed.

The repository is setup! You can now install packages.

  1. Below is the output for the install.
    output:
    sudo EXTERNAL_URL=“https://gitlabdev.testgl.com” zypper install gitlab-ee
    Refreshing service ‘SMT-http_smtsrv1_wakefern_com’.
    Loading repository data…
    Reading installed packages…
    ‘gitlab-ee’ is already installed.
    There is an update candidate for ‘gitlab-ee’, but it is from a different vendor. Use ‘zypper install gitlab-ee-13.10.0-ee.0.sles12.x86_64’ to install this candidate.
    Resolving package dependencies…

Nothing to do.

Hi @gitlab-greg,

I have followed the instructions in this article to update or refresh the gpg key.

I get the message below for one of the validation steps mentioned in the article that the package is nto installed.

sudo rpm -q gpg-pubkey-f27eab47-5cc36020 --qf ‘%{name}-%{version}-%{release} → %{summary}\n’
package gpg-pubkey-f27eab47-5cc36020 is not installed

It looks like an issue with the gpg key but it’s not getting updated automatically. I will try to update it manually and let you now.

Please let me know if you have any input on resolving this issue.

Thank you for your time.

sorry forgot to provide the link to the article in my earlier response. Here it is.

https://docs.gitlab.com/omnibus/update/package_signatures#package-repository-metadata-signing-keys

Hi @akaiserk, thanks for your patience.

The message you’re seeing is due to a change we made on our end to update the package vendor information.

This explains why you’re seeing a warning. Good news is that this is not a problem.

To upgrade, you can run:

zypper install gitlab-ee-13.10.0-ee.0.sles12.x86_64

Thank you, @gitlab-greg

1 Like

Am I right that upgrading gitlab can’t be done within the gitlab web interface, you need server level access?

@scmjerram yes, you have to do it from the server console either via SSH or directly from the server/VM itself - it cannot be done via web interface.

1 Like