Daily container scanning updates are broken

Summary

There's a daily scheduled pipeline (Build and publish new image with the latest advisory DB) in the container-scanning project that is in charge of triggering rebuilds of images.

This is important because the image contains the vulnerability database and we want this to be updated daily.

The scheduled pipeline sets the TRIGGER_DB_UPDATE CI variable, which is used in the CI configuration to trigger only one job: trigger-db-update.

The trigger-db-update job, in turn, finds the latest release and triggers a pipeline run for the corresponding tag.

Steps to reproduce

  1. Trigger the scheduled job: https://gitlab.com/gitlab-org/security-products/analyzers/container-scanning/-/pipeline_schedules/135105/play

Example Project

What is the current bug behavior?

  • Trigger of downstream pipeline fails
  • tag edge job runs

What is the expected correct behavior?

  • Trigger of downstream pipeline works
  • no other jobs run in the scheduled pipeline

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ó