Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8391

Closed
Open
Created Nov 25, 2014 by Administrator@rootOwner

Ruby version reporting in conflict

Created by: Libbux

I'm running GitLab 7.5 on Ubuntu 14.04. I used to be running an outdated version of ruby (see issue #8115 (closed) and #8146 (closed)), and since updating, GitLab has been showing the wrong ruby version in the web admin panel (it reports 1.9.3p484), while running the GitLab check rake task shows the following:

Ruby version >= 2.0.0 ? ... yes (2.0.0)

The ruby binary in /usr/bin/ points to the correct executable, and the service has been restarted multiple times since updating.

Thanks

Assignee
Assign to
Time tracking