404 Error Creating New Issue From User's "Issues" Page.
Please read this!
Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
For the Enterprise Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
Please remove this notice if you're confident your issue isn't a duplicate.
Summary
After clicking on the "Issues" in the left hand drop down for the logged-in user and presented with list of issues, clicking the green "New Issues" button after selecting a project in the drop down results in a 404 "undefined" error.
Steps to reproduce
Running: 9.4.1-ee
- Click "Issues" from left hand drop down, or hash "#" from top bar to open user's issue list.
- Click "New Issue" green button; select project from drop down list.
- 404 is presented. URL presents
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
What is the current bug behavior?
404 error
What is the expected correct behavior?
New Issue Dialog for the project you have selected.
Relevant logs and/or screenshots
From Production.Log
Started GET "/Web-Database-Development/barcode-scanner/undefined" for 128.151.32.241 at 2017-07-26 14:56:01 -0400
Processing by ApplicationController#route_not_found as HTML
Parameters: {"unmatched_route"=>"Web-Database-Development/barcode-scanner/undefined"}
Completed 404 Not Found in 23ms (Views: 13.1ms | ActiveRecord: 0.6ms | Elasticsearch: 0.0ms)
Output of checks
Locally hosted webserver
Results of GitLab environment info
System information
System: RedHatEnterpriseWorkstation 7.3
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Redis Version: 3.2.5
Git Version: 2.13.0
Sidekiq Version:5.0.0
Go Version: unknown
GitLab information
Version: 9.4.1-ee
Revision: 1ae0012
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
DB Version: 9.6.3
URL: https://xxx.xxx.gitlab.edu (output sanitized)
HTTP Clone URL: https://xxx.xxx.gitlab.edu/some-group/some-project.git
SSH Clone URL: git@xxx.xxx.gitlab.edu:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: yes
Using Omniauth: no
GitLab Shell
Version: 5.3.1
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
# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 5.3.1 ? ... OK (5.3.1)
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/3 ... repository is empty
21/5 ... ok
6/6 ... repository is empty
19/8 ... ok
12/9 ... ok
12/11 ... ok
10/12 ... ok
1/13 ... ok
26/14 ... ok
16/17 ... ok
12/18 ... ok
11/19 ... repository is empty
12/20 ... ok
3/22 ... repository is empty
20/23 ... ok
23/27 ... ok
23/28 ... ok
23/29 ... repository is empty
20/30 ... repository is empty
16/31 ... ok
21/33 ... repository is empty
26/34 ... ok
27/35 ... ok
12/36 ... ok
28/37 ... ok
12/38 ... ok
19/40 ... ok
12/41 ... ok
3/42 ... repository is empty
19/43 ... repository is empty
24/46 ... repository is empty
12/47 ... ok
16/48 ... ok
15/51 ... ok
19/52 ... repository is empty
14/54 ... ok
28/55 ... ok
35/56 ... ok
35/60 ... ok
41/62 ... ok
19/63 ... repository is empty
4/64 ... ok
14/65 ... ok
28/68 ... repository is empty
66/69 ... ok
56/70 ... ok
66/71 ... ok
14/73 ... ok
66/79 ... ok
66/80 ... ok
32/81 ... ok
66/82 ... ok
68/83 ... repository is empty
12/86 ... ok
67/87 ... ok
67/88 ... ok
67/90 ... ok
67/91 ... ok
67/92 ... ok
67/93 ... ok
67/94 ... ok
67/95 ... ok
67/96 ... ok
67/97 ... ok
67/98 ... ok
67/99 ... ok
67/100 ... ok
67/101 ... repository is empty
66/102 ... ok
66/104 ... ok
66/106 ... repository is empty
3/107 ... ok
66/108 ... ok
66/109 ... ok
66/110 ... ok
3/111 ... repository is empty
66/112 ... ok
66/113 ... ok
66/114 ... ok
66/115 ... ok
66/116 ... ok
66/117 ... repository is empty
66/118 ... ok
66/119 ... ok
66/120 ... ok
66/121 ... ok
66/122 ... ok
66/123 ... ok
66/124 ... ok
66/125 ... ok
66/126 ... ok
66/127 ... ok
66/128 ... ok
21/130 ... ok
71/131 ... ok
67/132 ... ok
12/133 ... repository is empty
71/134 ... repository is empty
21/135 ... repository is empty
82/136 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
Server: ldapmain
LDAP authentication... Anonymous. No `bind_dn` or `password` configured
LDAP users with access to your GitLab server (only showing the first 100 results)
<redacted>
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/3 ... yes
21/5 ... yes
6/6 ... yes
19/8 ... yes
12/9 ... yes
12/11 ... yes
10/12 ... yes
1/13 ... yes
26/14 ... yes
16/17 ... yes
12/18 ... yes
11/19 ... yes
12/20 ... yes
3/22 ... yes
20/23 ... yes
23/27 ... yes
23/28 ... yes
23/29 ... yes
20/30 ... yes
16/31 ... yes
21/33 ... yes
26/34 ... yes
27/35 ... yes
12/36 ... yes
28/37 ... yes
12/38 ... yes
19/40 ... yes
12/41 ... yes
3/42 ... yes
19/43 ... yes
24/46 ... yes
12/47 ... yes
16/48 ... yes
15/51 ... yes
19/52 ... yes
14/54 ... yes
28/55 ... yes
35/56 ... yes
35/60 ... yes
41/62 ... yes
19/63 ... yes
4/64 ... yes
14/65 ... yes
28/68 ... yes
66/69 ... yes
56/70 ... yes
66/71 ... yes
14/73 ... yes
66/79 ... yes
66/80 ... yes
32/81 ... yes
66/82 ... yes
68/83 ... yes
12/86 ... yes
67/87 ... yes
67/88 ... yes
67/90 ... yes
67/91 ... yes
67/92 ... yes
67/93 ... yes
67/94 ... yes
67/95 ... yes
67/96 ... yes
67/97 ... yes
67/98 ... yes
67/99 ... yes
67/100 ... yes
67/101 ... yes
66/102 ... yes
66/104 ... yes
66/106 ... yes
3/107 ... yes
66/108 ... yes
66/109 ... yes
66/110 ... yes
3/111 ... yes
66/112 ... yes
66/113 ... yes
66/114 ... yes
66/115 ... yes
66/116 ... yes
66/117 ... yes
66/118 ... yes
66/119 ... yes
66/120 ... yes
66/121 ... yes
66/122 ... yes
66/123 ... yes
66/124 ... yes
66/125 ... yes
66/126 ... yes
66/127 ... yes
66/128 ... yes
21/130 ... yes
71/131 ... yes
67/132 ... yes
12/133 ... yes
71/134 ... yes
21/135 ... yes
82/136 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.3)
Git version >= 2.7.3 ? ... yes (2.13.0)
Active users: ... 46
Elasticsearch version 5.1 - 5.3? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
Possible fixes
Unknown