Uploading artifacts as "archive" to coordinator... failed - 400 bad Request when not any expire_in is given

Summary

Hello,

First of all, we apologize for the lack of detail in this issue but we are having serious problems identifying the issue raised during our CI.

The upload to corrdinator failed with a 400 Bad Request.

Our gitlab is running on 13.11.3 CE and an upgrade to 13.12.3 is planned in week.

Steps to reproduce

• Setup python with sphinx
• Add .gitlab-ci.yml with deploy job
• Run CI on specified runner

.gitlab-ci.yml

stages:
  - deploy

pages:
  image: nikolaik/python-nodejs:python3.8-nodejs12
  stage: deploy

  before_script:
    # packages will be installed system wide after this line:
    - poetry config virtualenvs.create false
    - poetry install --no-root

  script:
    - sphinx-build -b html docs public

  artifacts:
    paths:
      - public
  only:
    - master

Actual behavior

Fail to publish archive via artifacts-uploader, raising unknonw and incomprehensible invalid argument error

Expected behavior

We hope the artifact is released, at least details to understand the error

Relevant logs and/or screenshots

job log

Uploading artifacts...
++ echo 'Uploading artifacts...'
++ /usr/bin/gitlab-runner-helper artifacts-uploader --url https://git.spikeelabs.fr/ --token [MASKED] --id 345405 --path public --artifact-format zip --artifact-type archive
public: found 118 matching files and directories   
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=345405 responseStatus=400 Bad Request status=400 token=YT1bcz9Q
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=345405 responseStatus=400 Bad Request status=400 token=YT1bcz9Q
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=345405 responseStatus=400 Bad Request status=400 token=YT1bcz9Q
FATAL: invalid argument

Environment description

Private installation of Gitlab using kubernetes and helm

Runner installation:

helm repo add gitlab https://charts.gitlab.io
helm repo update
helm upgrade --install -f gitlab-runner-chart/values.yaml --namespace gitlab-managed-apps gitlab-runner gitlab/gitlab-runner

values.yaml contents

certsSecretName: gitlab-domain-cert
gitlabUrl: https://git.spikeelabs.fr/
runnerRegistrationToken: ****
rbac:
  create: true
runners:
  tags: "kubernetes"
  runUntagged: true
  config: |
    [[runners]]
      pre_build_script = """
      apt-get update -y > /dev/null
      apt-get install -y ca-certificates > /dev/null
 
      cp /etc/gitlab-runner/certs/ca.crt /usr/local/share/ca-certificates/ca.crt
      update-ca-certificates --fresh > /dev/null
      """
      [runners.kubernetes]
      privileged = true
      [[runners.kubernetes.volumes.secret]]
        name = "gitlab-domain-cert"
        mount_path = "/etc/gitlab-runner/certs/"
        read_only = true
        [runners.kubernetes.volumes.secret.items]
          "git.spikeelabs.fr.crt" = "ca.crt"

Used GitLab Runner version

Our runner is under a kubernetes cluster using latest version of Gitlab Runner helm chart

Running with gitlab-runner 13.12.0 (7a6612da)
  on gitlab-runner-gitlab-runner-6b9bf76d77-l9l9m _f9TyXYX
Preparing the "kubernetes" executor
Using Kubernetes namespace: gitlab-managed-apps
Using Kubernetes executor with image nikolaik/python-nodejs:python3.8-nodejs12 ...

Possible fixes