Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #300604
Closed
Open
Issue created Feb 01, 2021 by Simeon Bobylev@meons

'Uploading artifacts as "archive" to coordinator... failed' after upgrade to 13.8.1

Summary

After upgrade to 13.8.1, artifacts upload is failing in CI pipelines. We are using object store as backend for artifacts.

Steps to reproduce

Upgrade to 13.8.1 with an object configuration for artifacts

Object store (anonymized) config:

gitlab_rails['object_store']['enabled'] = true
gitlab_rails['object_store']['proxy_download'] = true
gitlab_rails['object_store']['connection'] = {
  'provider'                => 'AWS',
  'aws_access_key_id'       => '',
  'aws_secret_access_key'   => '',
  'aws_signature_version'   => '2',
  'host'                    => 'host',
  'endpoint'                => 'https://endpoint',
  'path_style'              => true
}
[...]
gitlab_rails['object_store']['objects']['artifacts']['bucket'] = 'your_bucket'

What is the current bug behavior?

Uploading artifacts as "archive" to coordinator... failed

What is the expected correct behavior?

We should not facing those 404 errors.

Relevant logs and/or screenshots

CI pipeline log:

Uploading artifacts...
[...]                         
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1072517 responseStatus=400 Bad Request status=400 token=abc
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1072517 responseStatus=400 Bad Request status=400 token=abc
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1072517 responseStatus=400 Bad Request status=400 token=abc

Gitlab side (anonymized) log:

Expected(200) <=> Actual(404 Not Found)
excon.error.response
  :body          => "<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error><Code>NoSuchKey</Code></Error>"
  :cookies       => [
  ]
  :headers       => {
    "Accept-Ranges"    => "bytes"
    "Connection"       => "close"
    "Content-Length"   => "75"
    "Content-Type"     => "application/xml"
    "Date"             => "Mon, 01 Feb 2021 13:22:14 GMT"
    "Server"           => "Apache"
    "x-amz-request-id" => "tx00000000000002723e733-0000000000-35fb909-default"
  }
  :host          => "host"
  :local_address => "192.168.168.168"
  :local_port    => 44444
  :path          => "/path/my.file"
  :port          => 9999
  :reason_phrase => "Not Found"
  :remote_ip     => "1.2.3.4"
  :status        => 404
  :status_line   => "HTTP/1.1 404 Not Found\r\n"
Edited Feb 01, 2021 by Simeon Bobylev
Assignee
Assign to
Time tracking