I tried to upgrade my gitlab-ce 8.7.0 instance (installed from gitlab/sources) by minor version upgrades, but I got stuck because of strange bundle/gem issues and errors.
My v8.11.0 instance seems to work, but throws 500 entering any project. Other frontend-pages seem to work.
Gitlab check shows this:
System information
System: Debian 8.9
Current User: git
Using RVM: no
Ruby Version: 2.2.8p477
Gem Version: 2.7.2
Bundler Version:1.16.0
Rake Version: 10.5.0
Sidekiq Version:4.1.4
rake aborted!
NoMethodError: undefined methodissues_enabled=' for #<Project:0x9ce8a70> /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activemodel-4.2.7.1/lib/active_model/attribute_methods.rb:433:in
method_missing’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/default_value_for-3.0.2/lib/default_value_for.rb:178:inblock in set_default_values' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/default_value_for-3.0.2/lib/default_value_for.rb:154:in
each’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/default_value_for-3.0.2/lib/default_value_for.rb:154:inset_default_values' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:432:in
block in make_lambda’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:228:incall' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:228:in
block in halting_and_conditional’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:incall' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:in
block in call’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:ineach' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:506:in
call’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92:in__run_callbacks__' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in
_run_initialize_callbacks’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/core.rb:284:ininitialize' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/default_value_for-3.0.2/lib/default_value_for.rb:142:in
initialize’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/state_machines-activerecord-0.4.0/lib/state_machines/integrations/active_record.rb:463:ininitialize' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/inheritance.rb:61:in
new’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/inheritance.rb:61:innew' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/reflection.rb:141:in
build_association’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/associations/association.rb:250:inbuild_record' /home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/associations/collection_association.rb:146:in
build’
/home/git/gitlab/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.7.1/lib/active_record/associations/collection_proxy.rb:259:inbuild' /home/git/gitlab/lib/tasks/gitlab/info.rake:33:in
block (3 levels) in <top (required)>’
Tasks: TOP => gitlab:env:info
(See full trace by running task with --trace)
Because the “migration” is going to make me crazy the 5.th day “trying” now I also tried on another fresh ubuntu system to setup gitlab-ce 10.2 from source (all from scratch including db) to import only my repositories afterwards (loosing rest of my v8 database). The installation looks fine at first glance, but web-frontend does not even show login throwing error 500.
self check for 10.2 “try” looks like this:
Checking GitLab Shell …
GitLab Shell version >= 5.9.3 ? … OK (5.9.3)
Repo base directory exists?
default… yes
Repo storage directories are symlinks?
default… no
Repo paths owned by git:root, or git:git?
default… yes
Repo paths access is drwxrws—?
default… yes
hooks directories in repos are links: … can’t check, you have no projects
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OKAccess to /home/git/.ssh/authorized_keys: OK
gitlab-shell self-check successfulChecking GitLab Shell … Finished
Checking Sidekiq …
Running? … yes
Number of Sidekiq processes … 1Checking Sidekiq … Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP …LDAP is disabled in config/gitlab.yml
Checking LDAP … Finished
Checking GitLab …
Git configured correctly? … yes
Database config exists? … yes
All migrations up? … yes
Database contains orphaned GroupMembers? … no
GitLab config exists? … yes
GitLab config up to date? … yes
Log directory writable? … yes
Tmp directory writable? … yes
Uploads directory exists? … yes
Uploads directory has correct permissions? … yes
Uploads directory tmp has correct permissions? … skipped (no tmp uploads folder yet)
Init script exists? … yes
Init script up-to-date? … yes
Projects have namespace: … can’t check, you have no projects
Redis version >= 2.8.0? … yes
Ruby version >= 2.3.3 ? … yes (2.3.5)
Git version >= 2.7.3 ? … yes (2.7.4)
Git user has default SSH configuration? … yes
Active users: … 0Checking GitLab … Finished
I just need a working instance. Anyone knows how to fix one of the instances?