StoreSecurityReportsWorker sidekiq errors
Summary
~events/24hr | Error with sentry link | Could be fixed by schema validation? |
---|---|---|
900 | ActiveRecord::RecordNotUnique | No; Key (project_id, checksum) already exists |
50 | ActiveRecord::RecordInvalid | No; Validation failed: Issue can't be blank |
1,400 | NoMethodErrorSidekiq | Yes; identifiers are required, as is {identifier.name}
|
500 | ActiveRecord::RecordInvalid | Yes; metadata_version is called version in the schema, which is a required field |
250 | NoMethodErrorSidekiq | Maybe; report string doesn't match expectation that a colon is present for base_name, version = image.split(':') . Yes once #339078 (closed) is done. |
100 | Gitlab::Ci::Parsers::Security::Common::SecurityReportParserError | Yes. First iteration. |
Approximate # of events/24hr, Sentry link
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
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
Edited by Thiago Figueiró