[SOLVED] Gitlab CE Can't Connect to Gitlab CI for Merge Requests

I recently updated my GitlabCE (non Omnibus) installation to 7.10rc8, and my gitlab-CI installation to 7.9. New code pushed to gitlab builds just fine in CI, but I’m constantly presented with “Cannot Connect to the CI Server” when reviewing Merge requests.

Looking at the logs on the Gitlab CE server, I can’t find anything relevant. On the CI server, I see the following. I’m unsure of where to go from here, but it seems like this is a CI problem failing to return correct values to Gitlab?

Is there a version requirement between 7.10rc8 and GitlabCI? Should I revert Gitlab to 7.9?

Started GET "/projects/3/refs/SRE3112/commits/<commit_hash>/status.json?token=<token_id>" for 127.0.0.1 at 2015-04-24 14:40:17 -0600

ActionController::RoutingError (No route matches [GET] "/projects/3/refs/SRE3112/commits/40b87f52e6a9542d6575843384e2133460909c3d/status.json"):
  vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
  vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:38:in `call_app'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in `block in call'
  vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in `block in tagged'
  vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:26:in `tagged'
  vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/tagged_logging.rb:68:in `tagged'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/rack/logger.rb:20:in `call'
  vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.9/lib/action_dispatch/middleware/request_id.rb:21:in `call'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
  vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/engine.rb:514:in `call'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/application.rb:144:in `call'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in `public_send'
  vendor/bundle/ruby/2.0.0/gems/railties-4.1.9/lib/rails/railtie.rb:194:in `method_missing'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
  vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
  vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:572:in `process_client'
  vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:666:in `worker_loop'
  vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:521:in `spawn_missing_workers'
  vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:140:in `start'
  vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/bin/unicorn_rails:209:in `<top (required)>'
  vendor/bundle/ruby/2.0.0/bin/unicorn_rails:23:in `load'
  vendor/bundle/ruby/2.0.0/bin/unicorn_rails:23:in `<main>'

Can you try and upgrade to latest 7.10 stable?

CI is in the same package as GitLab so they always go on pair, no nned to do any check from your behalf.

1 Like

Updating to Gitlab 7.10.2, and GitlabCI 7.10.2 solved this issue.