[DRE-maint] Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Johannes Schauer]

Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

sorry for reporting another RC bug.

Because you were so quick in fixing #846916, I just upgraded my gitlab
chroot. Here are the relevant lines from my "apt-get upgrade" run
(showing all the package versions):

The following packages will be upgraded:
  bundler libjs-jquery-ui libruby2.3 libsqlite3-0 libsystemd0 libudev1 libustr-1.0-1 msmtp msmtp-mta ruby-bundler ruby-grape-entity ruby-molinillo ruby-rubypants ruby-temple ruby-thor ruby2.3 systemd systemd-sysv
18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7535 kB of archives.
After this operation, 169 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd amd64 232-7 [2452 kB]
Get:2 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsystemd0 amd64 232-7 [273 kB]
Get:3 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd-sysv amd64 232-7 [74.6 kB]
Get:4 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libudev1 amd64 232-7 [118 kB]
Get:5 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libustr-1.0-1 amd64 1.0.4-6 [76.3 kB]
Get:6 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsqlite3-0 amd64 3.15.2-1 [568 kB]
Get:7 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-molinillo all 0.5.0-2 [15.1 kB]
Get:8 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-thor all 0.19.1-3 [46.5 kB]
Get:9 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 bundler all 1.12.5-4 [35.5 kB]
Get:10 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-bundler all 1.12.5-4 [160 kB]
Get:11 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libjs-jquery-ui all 1.12.1+dfsg-2 [227 kB]
Get:12 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-grape-entity all 0.6.0-1 [24.5 kB]
Get:13 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-rubypants all 0.6.0-1 [9232 B]
Get:14 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-temple all 0.7.7-1 [29.7 kB]
Get:15 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libruby2.3 amd64 2.3.3-1 [3104 kB]
Get:16 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp amd64 1.6.6-1 [120 kB]
Get:17 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp-mta all 1.6.6-1 [15.2 kB]
Get:18 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby2.3 amd64 2.3.3-1 [186 kB]


When I now enter my gitlab instance I only get a 502 error with the
message "Whoops, GitLab is taking too much time to respond".

Since the last time I changed the version of a ruby package you told me
to run assets:precompile, I ran the following command:

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat /etc/gitlab/gitlab-debian.conf) && rake assets:precompile RAILS_ENV=production'
Could not find grape-entity-0.5.1 in any of the sources
Run `bundle install` to install missing gems.

Given the error above, I suspect that the new ruby-grape-entity version
is the culprit here.

Thanks!

cheers, josch