[go: up one dir, main page]

Skip to content

Sentry connection is not updating projects list

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When trying to link GitLab monitoring to a Sentry project, once the connection is established, the projects list dropdown does not seem to be updated.

Steps to reproduce

  • Create a GitLab project
  • Create a Sentry project (for example on Sentry cloud)
  • Try linking the GitLab monitoring service to the Sentry project (in Settings > Monitoring)
    • Create a valid auth token on the Sentry instance
    • Enter the Sentry URL
    • Enter the Sentry auth token
    • Click Connect
    • See the connection is successful
    • See the projects list dropdown is still disabled with no projects being listed

Example Project

Not applicable (private auth token).

What is the current bug behavior?

The Sentry projects list is empty.

What is the expected correct behavior?

The Sentry projects list should contain Sentry projects the auth token have access to once connection linked successfully.

Relevant logs and/or screenshots

image

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖