<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ## Status update (2023-01-19) - Issue closed. The problem was that report uploads were failing when metadata generation was enabled. This was fixed in (https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29151) by treating these as unsupported types for metadata generation, allowing report to function correctly again. ### Summary <!-- Summarize the bug encountered concisely. --> Pipeline fails on security scanning jobs such as [SAST](https://docs.gitlab.com/ee/user/application_security/sast/) or [IaC](https://docs.gitlab.com/ee/user/application_security/iac_scanning/) when the [artifact attestation](https://docs.gitlab.com/ee/ci/runners/configure_runners.html#artifact-attestation) feature is added. It fails to generate artifact metadata. Removing artifact attestation in the gitlab-ci.yml allows the pipeline to pass. ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> 1. Update GitLab Runner to 15.1 2. Create a `gitlab-ci.yml` file with a simple job 3. Add security scanning (IaC or SAST will do) 4. Add artifact attestation feature as a variable: ```yml variables: SECURE_LOG_LEVEL: "debug" RUNNER_GENERATE_ARTIFACTS_METADATA: "true" ``` 5. Run the pipeline. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ```yml stages: - build - test variables: SECURE_LOG_LEVEL: "debug" RUNNER_GENERATE_ARTIFACTS_METADATA: "true" build-code-job: stage: build script: - echo "Testing if artifacts metadata is generated:" artifacts: paths: - data.txt include: - template: Security/SAST-IaC.latest.gitlab-ci.yml artifacts: paths: - data2.txt ``` ### What is the current *bug* behavior? <!-- Describe what actually happens. --> When using artifact attestation with any security scanning such as [SAST](https://docs.gitlab.com/ee/user/application_security/sast/) or [IaC](https://docs.gitlab.com/ee/user/application_security/iac_scanning/) the [artifact attestation](https://docs.gitlab.com/ee/ci/runners/configure_runners.html#artifact-attestation) fails to generate artifact metadata with the error below: `only one file can be sent as raw ` The pipeline fails on the security scanning jobs. Pipelines with other jobs without scanning analyzers will pass. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Successfully ran jobs, downloaded artifacts and generated artifact attestation (metadata) ```shell Uploading artifacts... data.txt: found 1 matching files and directories Generating cache metadata Uploading artifacts as "archive" to coordinator... 201 Created id= responseStatus=201 Created token= Cleaning up project directory and file based variables 00:01 Job succeeded ``` ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ```shell Uploading artifacts for successful job 00:03 Uploading artifacts... gl-sast-report.json: found 1 matching files and directories Generating cache metadata ERROR: Uploading artifacts as "sast" to coordinator... error error=couldn't execute POST against ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.net/api/v4/jobs/88/artifacts?artifact_format=raw&artifact_type=sast: Post "▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.net/api/v4/jobs/88/artifacts?artifact_format=raw&artifact_type=sast": only one file can be sent as raw id=88 token=FdRJu1MA WARNING: Retrying... context=artifacts-uploader error=invalid argument ``` ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> The artifact attestation feature is available on GitLab Runner 15.1 <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (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`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (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) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->