Adding an issue to an epic using docker install gives - We can't find an issue that matches what you are looking for

Summary

Unable to add an issue to a Epic when using GitLab via a docker installation, when using an OS install you are able to the issue.

Steps to reproduce

  • Install GitLab 10.4.1 using the docker image.
  • All actions being done as the 'root' user.
  • Create a group
  • Create a project within the group
  • Create an issue in the project
  • Create an epic in the group
  • Add the issue via a link to the epic
  • ... gives error message

Tried various ways of assigning the issue using localhost, direct docker ip, hostname via /etc/hosts - all result in error.

Example Project

NA

What is the current bug behavior?

Unable to add an issue - error message returned is We can't find an issue that matches what you are looking for.

What is the expected correct behavior?

Able to add the issue.

Relevant logs and/or screenshots

==> /var/log/gitlab/gitlab-rails/production.log <==
Started POST "/groups/ultimate-projects/-/epics/1/issues" for 172.17.0.1 at 2018-01-29 23:10:50 +0000
Processing by Groups::EpicIssuesController#create as JSON
  Parameters: {"issue_references"=>["http://gitlab-ee-10.4.1:9090/ultimate-projects/proj-101/issues/1"], "group_id"=>"ultimate-projects", "epic_id"=>"1", "epi
c_issue"=>{}}
Completed 404 Not Found in 86ms (Views: 0.4ms | ActiveRecord: 36.5ms | Elasticsearch: 0.0ms)

==> /var/log/gitlab/gitlab-rails/production_json.log <==
{"method":"POST","path":"/groups/ultimate-projects/-/epics/1/issues","format":"json","controller":"Groups::EpicIssuesController","action":"create","status":40
4,"duration":87.95,"view":0.39,"db":36.47,"time":"2018-01-29T23:10:50.144Z","params":{"issue_references":["http://gitlab-ee-10.4.1:9090/ultimate-projects/proj
-101/issues/1"],"group_id":"ultimate-projects","epic_id":"1","epic_issue":{}},"remote_ip":"172.17.0.1","user_id":1,"username":"root"}

==> /var/log/gitlab/gitlab-workhorse/current <==
2018-01-29_23:10:50.23432 gitlab-ee-10.4.1:9090 @ - - [2018-01-29 23:10:50.108384738 +0000 UTC m=+37555.780596681] "POST /groups/ultimate-projects/-/epics/1/i
ssues HTTP/1.1" 404 3084 "http://gitlab-ee-10.4.1:9090/groups/ultimate-projects/-/epics/1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36
 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36" 0.125855

==> /var/log/gitlab/nginx/gitlab_access.log <==
172.17.0.1 - - [29/Jan/2018:23:10:50 +0000] "POST /groups/ultimate-projects/-/epics/1/issues HTTP/1.1" 404 1565 "http://gitlab-ee-10.4.1:9090/groups/ultimate-
projects/-/epics/1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36"

see attached screenshoots

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 
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.4.1-ee
Revision:       8959744
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.5
URL:            http://gitlab-ee-10.4.1
HTTP Clone URL: http://gitlab-ee-10.4.1/some-group/some-project.git
SSH Clone URL:  ssh://git@gitlab-ee-10.4.1:10022/some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: no


GitLab Shell
Version:        5.11.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.11.0 ? ... OK (5.11.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: ...
2/1 ... 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 ...


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? ... skipped (no tmp uploads folder yet)
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
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.7.3 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 1
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)


Checking GitLab ... Finished
epics-error-adding-issue-docker-install


epics-error-issue-docker-install

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by Mark Fletcher