Skip to content

List all epic notes API shows 404 when trying to access it using the URL-encoded path of the group

Summary

List all epic notes API shows 404 when trying to access it using the URL-encoded path of the group instead of the group ID.

Steps to reproduce

  • Create an epic, add some comments there (Epic notes are comments users can post to an epic)
  • Try to retrieve the notes using curl --request GET --header "PRIVATE-TOKEN: your_token" "https://gitlab-instance.tld/api/v4/groups/namespacepath/epics/epic_ID/notes"

What is the current bug behavior?

API request fails with 404.

What is the expected correct behavior?

API request should be completed successfully.

Relevant logs and/or screenshots

No errors are shown in the production.log.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:     Ubuntu 16.04
Proxy:      no
Current User:   git
Using RVM:  no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.3
Redis Version:  3.2.12
Git Version:    2.24.1
Sidekiq Version:5.2.7
Go Version: unknown


GitLab information
Version:    12.6.2-ee
Revision:   cf39803b81f
Directory:  /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 10.9
URL:        https://gitlabdomain.tld
HTTP Clone URL: https://gitlabdomain.tld/some-group/some-project.git
SSH Clone URL:  git@gitlabdomain.tld:some-group/some-project.git
Elasticsearch:  no
Geo:        no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:


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

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 10.3.0 ? ... OK (10.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


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


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab App ...


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: ...
...
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.22.0 ? ... yes (2.24.1)
Git user has default SSH configuration? ... yes
Active users: ... 41
Is authorized keys file accessible? ... yes
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

API request works as expected if one specifies group ID instead of URL-encoded path so it can be used as a workaround.

Related customer ticket: https://gitlab.zendesk.com/agent/tickets/143203 (internal only)

Edited by Alexandr Tanayno