Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P production
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 110
    • Issues 110
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • production
  • Issues
  • #1944
Closed
Open
Incident created Apr 15, 2020 by Stan Hu@stanhuMaintainer

High rate of 400 errors uploading CI artifacts

In https://gitlab.com/gitlab-org/omnibus-gitlab/-/jobs/512037445, I see:

WARNING: Uploading artifacts to coordinator... failed  id=512037445 responseStatus=400 Bad Request status=400 Bad Request token=BpRp2m-q
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts to coordinator... failed  id=512037445 responseStatus=400 Bad Request status=400 Bad Request token=BpRp2m-q
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts to coordinator... failed  id=512037445 responseStatus=400 Bad Request status=400 Bad Request token=BpRp2m-q

https://log.gprd.gitlab.net/goto/b7fbe05b7c251720664536af4fd40632 shows this:

image

This might be due to the security release yesterday, bu that should have updated Workhorse and restarted it.

Assignee
Assign to
Time tracking