Environments don't show up in Secret Variables "Environments" dropdown's search results

Summary

Environments that exist in the "Environments" page don't show up in the "Environments" dropdown of the Secret Variables configuration page for the project.

Steps to reproduce

  1. Create a project
  2. Create a dev branch and push it
  3. Observe that a dev Environment exists on the Environments page
  4. Go to the Secret Variables configuration page for the project
  5. Click the "Enivronments" dropdown and type dev in the Search bar
  6. Observe that no results display
  7. Observe that no XHR requests are shown in Developer Tools, and no errors are in the Console

Example Project

n/a

What is the current bug behavior?

The environments that exist don't show up in the "Environment" dropdown in the Secret Variables configuration for the project.

There are no XHR requests being sent during typing in the Search field.

What is the expected correct behavior?

Existing environments should show up in the "Environment" dropdown of the Secret Variables configuration for the project.

Any manually-created environment wildcards should also look different from actual existing Environments detected by the application, so a user knows the difference.

Relevant logs and/or screenshots

There are several Environments that exist: /BigTerminal/scala/invoice-sender-worker/environments: image

But they don't show up in the "Environments" dropdown of the Secret Variables configuration: /BigTerminal/scala/invoice-sender-worker/settings/ci_cd: image

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
root@gitlab:/# gitlab-rake gitlab:env:info

System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.3.6p384
Gem Version:    2.6.13
Bundler Version:1.13.7
Rake Version:   12.3.0
Redis Version:  3.2.11
Git Version:    2.14.3
Sidekiq Version:5.0.5
Go Version:     unknown


GitLab information
Version:        10.7.2-ee
Revision:       a4f29081
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.8
URL:            http://${GITLAB_HOST}
HTTP Clone URL: http://${GITLAB_HOST}/some-group/some-project.git
SSH Clone URL:  git@${GITLAB_HOST}:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: no


GitLab Shell
Version:        7.1.2
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 
root@gitlab:/# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...

GitLab Shell version >= 7.1.2 ? ... OK (7.1.2)
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: ...
4/1 ... ok
4/2 ... 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: ...
4/1 ... yes
4/2 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 2
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)


Checking GitLab ... Finished

Possible fixes

No idea

Edited by Neil Hooey