OCS vulns that were previously resolved but are detected again are not set as detected

Summary

OCS vulns that were previously resolved but are detected again are not set as detected

Steps to reproduce

  1. Run an OCS scan on a resource with known vulns, note the number of vulns created in the dashboard
  2. Manually resolve one of the vuln
  3. Run the OCS scan again and note that the number of vulns in the dashboard did not change back to the same number as step 1

What is the current bug behavior?

Vulns that were resolved but are detected again are not set as detected

What is the expected correct behavior?

Vulns that were resolved but are detected again should be set as detected

Relevant logs and/or screenshots

Output of checks

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