Failure in ee/browser_ui/10_govern/vulnerability_management_spec.rb | Govern Vulnerability management in a merge request can create an issue from a security finding in pipeline security tab

Full description

Govern Vulnerability management in a merge request can create an issue from a security finding in pipeline security tab

File path

./qa/specs/features/ee/browser_ui/10_govern/vulnerability_management_spec.rb

Stack trace

Failure/Error:
  Resource::ProjectRunner.fabricate! do |runner|
    runner.project = project
    runner.name = "runner-for-#{project.name}"
    runner.tags = ['secure_report']
  end

RuntimeError:
  Failed to GET https://gitlab.com/api/v4/projects/gitlab-qa-sandbox-group-3%2Fqa-test-2023-04-18-23-35-39-b24ca37d0148442d%2Fproject-with-security-findings-8235a166b743a3c3/runners?tag_list=secure_report&private_token=[****] - (404): `{"message":"404 Project Not Found"}`.

First happened in https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/9808794.

Related test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/383756.

added Enterprise Edition QA Quality failurenew found:canary.gitlab.com priority2 test labels

Failed most recently in staging pipeline: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9907508

changed due date to May 19, 2023

assigned to @hmuralidhar

This issue was automatically tagged with the label groupthreat insights by TanukiStan, a machine learning classification model, with a probability of 1.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

added automation:ml groupthreat insights labels

added devopsgovern sectionsec labels

Seems to be a new error as previous failures for this test have been related to qa-bot account being blocked.

mentioned in issue gitlab-org/quality/pipeline-triage#194 (closed)

mentioned in issue gitlab-org/quality/pipeline-triage#195 (closed)

added found:pre.gitlab.com label

mentioned in issue gitlab-org/quality/testcase-sessions#69555 (closed)

added found:canary.staging.gitlab.com label

added found:staging.gitlab.com label

mentioned in issue gitlab-org/quality/testcase-sessions#69707 (closed)

mentioned in issue gitlab-org/quality/testcase-sessions#69709 (closed)

mentioned in issue #411048 (closed)

Env issue

closed