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

Closed
Open
Created Jul 25, 2014 by Administrator@rootOwner

[Gitlab 7.1] 422 when trying to transfer project to other namespace

Created by: Wachiwi

Summary: Getting a 422 (The change you wanted was rejected.) when transfering a project to other namespace after upgrade to 7.1

Steps to reproduce:

  1. Create a project in Gitlab 7.0 with the visibility internal
  2. Upgrade to Gitlab 7.1
  3. Try to transfer the project via adminarea to other namespace

Expected behavior: The project should be transferred to the other namespace as planned

Observed behavior: When trying to transfer the project to the new namespace, I recieve a 422 (see below)

capture

If I create a new project in Gitalb 7.1 with visibility internal I can transfer it.

Relevant logs and/or screenshots:

  • nginx logs have nothing special
  • production/application/sattelites have nothing special

Output of checks:

[root] bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:         CentOS 6.5
Current User:   root
Using RVM:      no
Ruby Version:   2.1.2p95
Gem Version:    2.4.1
Bundler Version:1.5.3
Rake Version:   10.3.2
Sidekiq Version:2.17.0

GitLab information
Version:        7.1.0
Revision:       68a9203
Directory:      /var/lib/git/gitlab
DB Adapter:     mysql2
URL:            https://example.com
HTTP Clone URL: https://example.com/some-project.git
SSH Clone URL:  [email protected]:some-project.git
Using LDAP:     yes
Using Omniauth: no

GitLab Shell
Version:        1.9.6
Repositories:   /path/to/repos
Hooks:          /var/lib/git/gitlab-shell/hooks/
Git:            /usr/local/bin/git
[root] sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...

Git configured for git user? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.9.6 ? ... OK (1.9.6)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
Satellites access is drwxr-x---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ...

<projects: all ok>

Running /var/lib/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
        /path/to/repo: OK
        /var/lib/git/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 2.4.10
Send ping to redis server: PONG
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking LDAP ...

<removed ldap users>

Checking LDAP ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
Database contains orphaned UsersGroups? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...

<projects: all ok>

Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/local/bin/git"
Git version >= 1.7.10 ? ... yes (1.9.0)

Checking GitLab ... Finished

Possible Fixes:

IfI change the visibility from internal to private and try to transfer again it works!

Assignee
Assign to
Time tracking