Blank password on Jira service template prevents users from initializing new repository

Summary

Can not create master (or any other) branch in freshly created project. Committing a README.md via web UI returns "You are not allowed to push into this branch".

Steps to reproduce

  • Via the Web UI, navigate to a sub group and click "New Project"
  • Project is "private", as defined by the parent group
  • Follow instructions to create a README.md via the web editor
  • Click on "commit"
  • Enjoy error message "You are not allowed to push into this branch"

On local machine:

git clone git@gitlab.domain.com:group/subgroup/project.git
cd project
// create some files
git add .
git commit -m "Init"
git push -u origin master

Counting objects: 3, done.
Writing objects: 100% (3/3), 229 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: GitLab: You are not allowed to push code to protected branches on this project.
To git@gitlab.domain.com:group/subgroup/project.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@gitlab.domain.com:group/subgroup/project.git'

Example Project

Can not reproduce the issue on Gitlab.com

What is the current bug behavior?

Can not create master branch.

What is the expected correct behavior?

Master branch should be created to be able to use the repository.

Relevant logs and/or screenshots

root@gitlab1-0> tail -f /var/log/gitlab/gitlab-rails/application.log
November 24, 2017 10:08: group created a new project "group / subgroup / project"

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 


gitlab-rake gitlab:env:info




System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.3.5p376
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.1.0
Redis Version:	3.2.5
Git Version:	2.13.6
Sidekiq Version:5.0.4
Go Version:	unknown


GitLab information
Version:	10.2.1
Revision:	eb2643f
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://gitlab.domain.com
HTTP Clone URL:	https://gitlab.domain.com/some-group/some-project.git
SSH Clone URL:	git@gitlab.domain.com:some-group/some-project.git
Using LDAP:	yes
Using Omniauth:	no


GitLab Shell
Version:	5.9.4
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 


gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...




GitLab Shell version >= 5.9.4 ? ... OK (5.9.4)
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: ...
2/1 ... ok
3/2 ... ok
5/3 ... ok
4/4 ... ok
3/5 ... ok
3/6 ... ok
3/7 ... ok
3/8 ... ok
7/10 ... ok
7/11 ... ok
7/12 ... ok
7/13 ... ok
7/14 ... ok
7/15 ... ok
7/16 ... ok
7/17 ... ok
7/18 ... ok
7/19 ... ok
7/20 ... ok
7/21 ... ok
7/22 ... ok
7/23 ... ok
7/24 ... ok
7/25 ... ok
7/26 ... ok
7/27 ... ok
7/28 ... ok
7/29 ... ok
7/30 ... ok
7/31 ... ok
7/32 ... ok
7/33 ... ok
6/34 ... ok
2/35 ... ok
2/36 ... ok
6/37 ... ok
6/38 ... ok
2/39 ... ok
9/40 ... ok
9/41 ... ok
9/42 ... ok
9/43 ... ok
6/44 ... ok
7/45 ... ok
2/46 ... ok
10/47 ... ok
10/48 ... ok
10/49 ... ok
10/50 ... ok
10/51 ... ok
10/52 ... ok
10/53 ... ok
10/54 ... ok
10/56 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


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


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


(...snip...)


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? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
2/1 ... yes
3/2 ... yes
5/3 ... yes
4/4 ... yes
3/5 ... yes
3/6 ... yes
3/7 ... yes
3/8 ... yes
7/10 ... yes
7/11 ... yes
7/12 ... yes
7/13 ... yes
7/14 ... yes
7/15 ... yes
7/16 ... yes
7/17 ... yes
7/18 ... yes
7/19 ... yes
7/20 ... yes
7/21 ... yes
7/22 ... yes
7/23 ... yes
7/24 ... yes
7/25 ... yes
7/26 ... yes
7/27 ... yes
7/28 ... yes
7/29 ... yes
7/30 ... yes
7/31 ... yes
7/32 ... yes
7/33 ... yes
6/34 ... yes
2/35 ... yes
2/36 ... yes
6/37 ... yes
6/38 ... yes
2/39 ... yes
9/40 ... yes
9/41 ... yes
9/42 ... yes
9/43 ... yes
6/44 ... yes
7/45 ... yes
2/46 ... yes
10/47 ... yes
10/48 ... yes
10/49 ... yes
10/50 ... yes
10/51 ... yes
10/52 ... yes
10/53 ... yes
10/54 ... yes
10/56 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.6)
Git user has default SSH configuration? ... yes
Active users: ... 3


Checking GitLab ... Finished

Possible fixes

None

Edited by Patrick Deuley