Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

Thanks for confirmation. Closing this bug.

I just tested your new version 14.8.5+ds1-1~fto11+2. Unfortunately, in 
the gitlab-rake command script, the export of GEM_HOME is missing, 
causing the script to fail. After adding GEM_HOME to the list of 
exports, I can run commands like gitlab-rake gitlab:check".


Best,

Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

So I will wait if anyone else can confirm or reproduce this issue 
before adding GEM_PATH. Did you have GEM_HOME set in 
/etc/gitlab/gitlab-debian.conf ?


No, actually not. I now tested with

  GEM_HOME=/var/lib/gitlab/.gem

and I can confirm that this alone suffices. So, setting GEM_PATH is not 
needed when GEM_HOME is set correctly.


Best,
Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

Run 'gem env gempath' and set GEM_PATH variable with this value and 
/var/lib/gitlab/.gem added in /etc/gitlab/gitlab-debian.conf

I will try to do this automatically too.



This has indeed worked immediately. Thank you very much for the fast 
support!


Best
Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

A little addition: To also get gitlab-rake working, I needed to add 
GEM_PATH to the list of exported variables in /usr/sbin/gitlab-rake.


Best,
Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

Package: gitlab
Version: 14.7.7+ds1-2~fto11+2
Severity: normal

Dear Maintainer,

Recently, I tried to upgrade Gitlab to 14.7.7+ds1-2~fto11+2.
Unfortunately, gitlab-sidekiq does not start afterwards but fails as
it cannot find graphiql-rails:

gitlab-sidekiq[8334]: Could not find gem 'graphiql-rails (~> 1.8)' in any 
of the gem sources listed in your Gemfile

However, in /var/lib/gitlab/.gem/gems (I fixed the owner as described
in the wiki), the gem is present (in directory graphiql-rails-1.8.0).
Unfortunately, I cannot uninstall the apt package ruby-graphiql-rails
(version 1.4.10-1) as gitlab still depends on it.

So, I assumed that Gitlab finds the graphiql-rails package installed
by apt. After I had updated the Gemfile to require version 1.4 of
graphiql-rails, I can indeed successfully start gitlab-sidekiq.

With this, Gitlab starts again, however some features do not work.
Most notably, I cannot merge a morge request anymore.

Thanks for your support!

Best,
Maximilian