Skip to content

Gitlab 14.4 upgrade fails "PG::InvalidObjectDefinition: ERROR: functions in index predicate must be marked IMMUTABLE"

Summary

Upgraded Gitlab 14.3.3-ce.0.el8 to 14.4.0-ce.0.el8 via yum update gitlab-ce.

Once the upgrade completed Gitlab was not running.

Steps to reproduce

yum update gitlab-ce

Example Project

N/A

What is the current bug behavior?

Gitlab fails to start.

Output from gitlab-rake db:migrate --trace gitlab-rake-db_migrate-output.txt

What is the expected correct behavior?

Database migration should complete successful and Gitlab should start

Relevant logs and/or screenshots

Attached above

Output of checks

N/A

Results of GitLab environment info

Expand for output related to GitLab environment info
[root@ANISE gitlab]# gitlab-rake gitlab:env:info

System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.7.4p191
Gem Version:    3.1.4
Bundler Version:2.1.4
Rake Version:   13.0.6
Redis Version:  6.0.14
Git Version:    2.33.0.
Sidekiq Version:6.2.2
Go Version:     unknown

GitLab information
Version:        14.4.0
Revision:       51b27ab5805
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     12.7
URL:            https://git.pickysysadmin.ca
HTTP Clone URL: https://git.pickysysadmin.ca/some-group/some-project.git
SSH Clone URL:  git@git.pickysysadmin.ca:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: github, google_oauth2

GitLab Shell
Version:        13.21.1
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

This might be related but I have no idea how to implement it on my installation: #339091 (closed)