Identity provider form field is an empty dropdown

Summary

When adding a new identity for a user, the form field used to enter the Provider is a empty dropdown instead of a regular input field. This does not allow an admin to choose or add a provider. When using Chrome dev tools to change the select to an input field, I can submit the form and the identity is saved properly.

Steps to reproduce

1. Log in as an admin user
2. Go to https://your.git.lab/admin/users/{username}/identities/new for any user
3. Observe the empty dropdown for the provider field

Example Project

n/a

What is the current bug behavior?

It is not possible to enter a provider when adding an Identity for a GitLab user.

What is the expected correct behavior?

The provider should be an input field.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment 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.0.0
Redis Version:	3.2.5
Git Version:	2.13.5
Sidekiq Version:5.0.4
Go Version:	unknown
GitLab information
Version:	10.0.2
Revision:	06a5a33
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://git.xxxxxxx
HTTP Clone URL:	https://git.xxxxxxx/some-group/some-project.git
SSH Clone URL:	git@git.xxxxxxx:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no
GitLab Shell
Version:	5.9.0
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

Checking GitLab Shell ...
GitLab Shell version >= 5.9.0 ? ... OK (5.9.0)
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: ...
3/1 ... ok
3/3 ... ok
12/4 ... ok
4/5 ... ok
4/6 ... ok
4/7 ... ok
3/8 ... ok
3/10 ... ok
3/11 ... ok
3/12 ... ok
3/13 ... ok
7/14 ... ok
7/15 ... ok
7/16 ... ok
12/17 ... ok
4/18 ... ok
12/19 ... repository is empty
3/21 ... ok
5/22 ... ok
18/26 ... ok
5/28 ... ok
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 ...
LDAP is disabled in config/gitlab.yml
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: ...
3/1 ... yes
3/3 ... yes
12/4 ... yes
4/5 ... yes
4/6 ... yes
4/7 ... yes
3/8 ... yes
3/10 ... yes
3/11 ... yes
3/12 ... yes
3/13 ... yes
7/14 ... yes
7/15 ... yes
7/16 ... yes
12/17 ... yes
4/18 ... yes
12/19 ... yes
3/21 ... yes
5/22 ... yes
18/26 ... yes
5/28 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.5)
Git user has default SSH configuration? ... yes
Active users: ... 9
Checking GitLab ... Finished

Possible fixes

n/a