Skip to content

MR Vulnerabilities Error creating Issue on Staging

Summary

MR Vulnerabilities Error creating Issue on Staging

The API call to -/vulnerability_feedback returns a 500

This is seen on Sentry https://sentry.gitlab.net/gitlab/staginggitlabcom/issues/1172625/?query=is%3Aunresolved%20vulnerability_feedback

as ERROR: pgbouncer cannot connect to server

Steps to reproduce

  1. Populate a project in Staging
  2. Introduce an MR with vulnerabilities
  3. Select a vulnerability in the MR and select Create Issue
  4. Note error

Example Project

https://staging.gitlab.com/gitlab-qa-sandbox-group/qa-test-2020-11-17-16-40-27-dbce95f60e2ac0fb/project-with-secure-af2d0d60931da122/-/merge_requests/1

What is the current bug behavior?

The API call to -/vulnerability_feedback returns a 500, an error is shown

What is the expected correct behavior?

The API call to -/vulnerability_feedback is successful, an issue is created

Relevant logs and/or screenshots

image

Output of checks

Staging

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