Failure in browser_ui/10_govern/scan_result_policy_vulnerabilities_spec.rb | Govern Scan result policy requires approval when a pipeline report has findings matching the scan result policy

Summary

Failing job(s): https://gitlab.com/gitlab-org/gitlab/-/jobs/5289982647

Failing spec(s): Govern Scan result policy requires approval when a pipeline report has findings matching the scan result policy

Corresponding test case(s): https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/365005

Stack trace

 1) Govern Scan result policy requires approval when a pipeline report has findings matching the scan result policy
     Failure/Error:
       EE::Resource::SecurityScanPolicyProject.fabricate_via_api! do |commit|
         commit.full_path = project.full_path
       end
     
     QA::Resource::Errors::ResourceFabricationFailedError:
       Fabrication of QA::EE::Resource::SecurityScanPolicyProject using the API failed (200) with `{"data":{"securityPolicyProjectCreate":{"project":null,"errors":["Project was created and assigned as security policy project, but failed adding users to the project."]}}}`.
       Correlation Id: 01HCMXVR5AA2RHMTJ5XMJ4NQBE
     # ./qa/resource/api_fabricator.rb:121:in `api_post_to'
     # ./qa/resource/api_fabricator.rb:107:in `api_post'
     # ./qa/resource/api_fabricator.rb:29:in `fabricate_via_api!'
     # ./qa/resource/base.rb:73:in `block (2 levels) in fabricate_via_api!'
     # ./qa/resource/base.rb:108:in `log_and_record_fabrication'
     # ./qa/resource/base.rb:73:in `block in fabricate_via_api!'
     # ./qa/resource/base.rb:98:in `do_fabricate!'
     # ./qa/resource/base.rb:72:in `fabricate_via_api!'
     # ./qa/specs/features/ee/browser_ui/10_govern/scan_result_policy_vulnerabilities_spec.rb:27:in `block (3 levels) in <module:QA>'
     # ./qa/specs/spec_helper.rb:132:in `block (2 levels) in <top (required)>'
     # /home/gitlab/spec/support/fast_quarantine.rb:22:in `block (2 levels) in <top (required)>'
     # ./qa/specs/knapsack_runner.rb:17:in `run'
     # ./qa/specs/runner.rb:57:in `perform'
     # ./qa/scenario/template.rb:10:in `block in perform'
     # ./qa/scenario/template.rb:8:in `perform'
     # ./qa/scenario/template.rb:50:in `perform'
     # ./qa/scenario/template.rb:10:in `block in perform'
     # ./qa/scenario/template.rb:8:in `perform'
     # ./qa/scenario/bootable.rb:52:in `launch!'

Possible fixes

Reports (3)

1. 2023-10-17: https://gitlab.com/gitlab-org/gitlab/-/jobs/5314430428 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1040218483)
2. 2023-11-13: https://gitlab.com/gitlab-org/gitlab/-/jobs/5518104992 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1069723096)
3. 2023-11-13: https://gitlab.com/gitlab-org/gitlab/-/jobs/5518597497 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1069782250)

changed due date to October 27, 2023

added QA Quality devopsgovern failurenew found:master test typeignore labels

added sectionsec label

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

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

changed the description

added Enterprise Edition found:main labels

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

changed the description

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

changed the description

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

Happened on main: https://gitlab.com/gitlab-org/gitlab/-/jobs/5518104992

Passed on retry: https://gitlab.com/gitlab-org/gitlab/-/jobs/5518578711

cc @hmuralidhar

added failureflaky-test label and removed failurenew label

Another occurrence today: https://gitlab.com/gitlab-org/gitlab/-/jobs/5518597497

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

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

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

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

This issue has not received any updates in 90 days. It will now be closed!

closed

added auto closed label