Error connecting to database during debian wheezy->jessie omnibus package update
Summary
Connection to database during debian omnibus wheezy->jessie package upgrade fails
Steps to reproduce
From installed debian wheezy omnibus gitlab ce instance, change instances of 'wheezy' in apt sources lists (source.list and the list containing gitlab repository) to 'jessie', run apt-get upgrade
.
e.g. 'deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ wheezy main' -> 'deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ jessie main'
What is the current bug behavior?
Upgrade fails attempting to backup the database, with error 'FATAL: Peer authentication failed for user "gitlab"'. Certainly a database must exist from the current gitlab omnibus installation. Skipping the database backup is undesirable, and I wouldn't be surprised if using 'skip-auto-migrations' might cause the upgrade to fail in an even nastier place later in the same way.
What is the expected correct behavior?
In-place upgrade should complete successfully, including database backup.
Relevant logs
Relevant logs
Preparing to unpack .../gitlab-ce_10.5.2-ce.0_amd64.deb ... gitlab preinstall: gitlab preinstall: This node does not appear to be running a database gitlab preinstall: Skipping version check, if you think this is an error exit now gitlab preinstall: gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!) rake aborted! PG::ConnectionBad: FATAL: Peer authentication failed for user "gitlab" /opt/gitlab/embedded/service/gitlab-rails/app/models/application_setting.rb:262:in `ensure_cache_setup' /opt/gitlab/embedded/service/gitlab-rails/app/models/application_setting.rb:255:in `cached' /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/current_settings.rb:34:in `cached_application_settings' /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/current_settings.rb:29:in `ensure_application_settings!' /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/current_settings.rb:8:in `current_application_settings' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:13:in `block (2 levels) in ' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:21:in `block (2 levels) in ' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:99:in `block (2 levels) in ' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:91:in `block in ' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:74:in `' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:2:in `' /opt/gitlab/embedded/service/gitlab-rails/lib/api/groups.rb:1:in `' /opt/gitlab/embedded/service/gitlab-rails/lib/api/api.rb:123:in `' /opt/gitlab/embedded/service/gitlab-rails/lib/api/api.rb:2:in `' /opt/gitlab/embedded/service/gitlab-rails/lib/api/api.rb:1:in `' /opt/gitlab/embedded/service/gitlab-rails/config/initializers/rack_attack.rb:12:in `' /opt/gitlab/embedded/service/gitlab-rails/config/environment.rb:5:in `' /opt/gitlab/embedded/bin/bundle:23:in `load' /opt/gitlab/embedded/bin/bundle:23:in `' Tasks: TOP => gitlab:backup:create => gitlab_environment => environment (See full trace by running task with --trace) gitlab preinstall: gitlab preinstall: Backup failed! If you want to skip this backup, run the following command and gitlab preinstall: try again: gitlab preinstall: gitlab preinstall: sudo touch /etc/gitlab/skip-auto-migrations gitlab preinstall: dpkg: error processing archive /var/cache/apt/archives/gitlab-ce_10.5.2-ce.0_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1
Details of package version
Provide the package version installation details
gitlab-ce 10.5.1-ce.0
Environment details
- Operating System: debian
- Installation Target, remove incorrect values:
- VM: KVM
- Installation Type, remove incorrect values:
- Upgrade from version 10.5.1-ce.0/wheezy to 10.5.2-ce.0/jessie
- Is there any other software running on the machine: no
- Is this a single or multiple node installation? single
- Resources
- CPU: 3xQEMU Virtual CPU version 2.1.2
- Memory total: 6GB
Configuration details
No specific database related configuration, just default omnibus settings.