UNCLASSIFIED - NO CUI

Skip to content

Uploading artifacts to coordinator returns "responseStatus=400 Bad Request" during pipeline "Import artifacts" phase

I'm trying to run an initial container hardening pipeline on the matlab-with-desktop project and I appear to be running into a GitLab pipeline bug that exhibits as follows

...
INFO: Generating checksum
INFO: comparing checksum values: af09852b5c2c5760f7e5ce0da7deaf48fe26bd72042a4f5cea2fd2906fdd1bca vs af09852b5c2c5760f7e5ce0da7deaf48fe26bd72042a4f5cea2fd2906fdd1bca
INFO: Checksum verified
INFO: File saved as 'matlab.tar.gz'
Uploading artifacts for successful job
21:17
Uploading artifacts...
ci-artifacts/import-artifacts/: found 8 matching files and directories 
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1320666 responseStatus=400 Bad Request status=400 token=jySp95Nq
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1320666 responseStatus=400 Bad Request status=400 token=jySp95Nq
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1320666 responseStatus=400 Bad Request status=400 token=jySp95Nq
FATAL: invalid argument                            
Cleaning up file based variables
00:02
ERROR: Job failed: command terminated with exit code 1

Particularly, whilst undertaking upload of artifacts (that have successfully been downloaded from AWS and been SHA256 verified), the coordinator seems to be returning a 400 code, rather than allowing upload.

This issue looks pretty similar to the following reported bug #1651 in GitLab; this links to production issue #1944 for GitLab which appears to be how they fixed the underlying problem.

I don't think the issue I see relates to any code I've submitted to the repo. Is there something I can do to alleviate this and get onto the next stage of the pipeline or is this a bug in GitLab? It is worth noting that matlab.tar.gz is large (at 5.2GB).

Edited by Jos Martin