Unable to upgrade to gitlab 12.6.0 on ubuntu 18.04.3 lts

How to Use GitLab Upgrade
1

When i run sudo apt update and sudo apt upgrade. ubuntu is unable to upgrade gitlab-ee12.6.0

screenshot terminal: https://ibb.co/B631C0j

2

Hi,

as it seems from your screenshot, you tried upgrading from a Gitlab version earlier than 12. If that is really the case, you first need to upgrade your Gitlab instance to Gitlab 11.

You can do this by executing this:

sudo apt-get install gitlab-ee=11.11.0-ce.0

After upgrading to Gitlab 11.11, you can resume your normal upgrade path.

In order to ensure easy upgrades, consider upgrading regularly :wink:

Best Regards

1 Like
3

Thx ill try this as soon as I get home. Normally i regurarly do sudo apt uodate and upgrade but i was switching servers and vms so that might be the reason for outdated version.

4

Currently i’m facing the same problem.

so i’m at gitlab-ee 14.8.2 and apparently my regulary sudo apt update apt upgrade isn’t that updating as expected.

so i tried sudo apt install gitlab-ee=14.10.5-ce.0 but it says gitlab-ee not found what to do best from here? I alreaedy have backupped.

5

Oke never mind I managed to upgrade, however from the latest 15.x.x version listed in the upgrade path till 15.11.1 i’m getting an error. seems like an error with the database.

when doing a sudo apt upghrade it wanted too upgrade from 15.11.1 to 15.11.3 with invalid gituser.json.

currently my gitlab says version 15.11.1 however this is the failed upgrade version.

main: == 20221011162637 AddPartialIndexProjectIncidentManagementSettingsOnProjectIdAndSlaTimer: migrating
main: – transaction_open?()
main: → 0.0000s
main: – view_exists?(:postgres_partitions)
main: → 0.0011s
main: – index_exists?(:project_incident_management_settings, :project_id, {:name=>“index_project_incident_management_settings_on_p_id_sla_timer”, :where=>“sla_timer = TRUE”, :algorithm=>:concurrently})
main: → 0.0026s
main: – execute(“SET statement_timeout TO 0”)
main: → 0.0003s
main: – add_index(:project_incident_management_settings, :project_id, {:name=>“index_project_incident_management_settings_on_p_id_sla_timer”, :where=>“sla_timer = TRUE”, :algorithm=>:concurrently})
main: → 0.0070s
main: – execute(“RESET statement_timeout”)
main: → 0.0004s
main: == 20221011162637 AddPartialIndexProjectIncidentManagementSettingsOnProjectIdAndSlaTimer: migrated (0.0204s)

main: == 20221011210455 AddUseLegacyWebIdeToUserPreferences: migrating ==============
main: – add_column(:user_preferences, :use_legacy_web_ide, :boolean, {:default=>false, :null=>false})
main: → 0.0018s
main: == 20221011210455 AddUseLegacyWebIdeToUserPreferences: migrated (0.0023s) =====

main: == 20221012033107 AddPasswordLastChangedAtToUserDetails: migrating ============
main: – add_column(:user_details, :password_last_changed_at, :datetime_with_timezone, {:comment=>“JiHu-specific column”})
main: → 0.0012s
main: == 20221012033107 AddPasswordLastChangedAtToUserDetails: migrated (0.0014s) ===

main: == 20221012135524 AddScanFilePathLimitForDastSiteProfile: migrating ===========
main: – transaction_open?()
main: → 0.0000s
main: – transaction_open?()
main: → 0.0000s
main: – execute(“ALTER TABLE dast_site_profiles\nADD CONSTRAINT check_8d2aa0f66d\nCHECK ( char_length(scan_file_path) <= 1024 )\nNOT VALID;\n”)
STDERR:
---- End output of “bash” ----

I can provide the full stacktrace if needed