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
  • #7359

Closed
Open
Created Jul 23, 2014 by Administrator@rootOwner

Merge request can't be merged sometimes

Created by: randaalex

Sometimes (in random periods) gitlab can't merge all MergeRequests (Merge button inactive). In log we have the following error:

July 23, 2014 10:16 -> ERROR -> Command failed [1]: /usr/bin/git --git-dir=/home/git/gitlab-satellites/activebilling/core/.git checkout -b master origin/master

error: The following untracked working tree files would be overwritten by checkout:
        db/migrate/20140721135259_add_account_id_to_notes.rb
        db/migrate/20140722075207_add_allow_subdomain_to_dns_domains.rb
        db/migrate/20140722081127_add_attachment_to_notes.rb
        db/migrate/20140722081319_drop_note_attachments.rb
        vendor/assets/javascripts/ng-upload.js
Please move or remove them before you can switch branches.
Aborting
Our environment is:
Ubuntu 12.04.3 LTS
GitLab 6.8.1
GitLab Shell 1.9.3
GitLab API v3
Ruby 2.0.0p353
Rails 4.0.3

Currently we resolve this issue by rebuilding satellites and reopen each MR. Any ideas how to fix this problem?

This issue also copied to https://gitlab.com/gitlab-org/gitlab-ce/issues/442

Assignee
Assign to
Time tracking