Docker registry produces incomplete multipart uploads

Solution Verified - Updated -

Issue

  • When using the oc new-app to create a new build, the builds are creating incomplete multipart uploads to S3 when the build is completed successfully.

    [yyyy-mm-dd hh:mm:ss CET]     0B registry/docker/registry/v2/repositories/e2e-1545143177-hqaqbs55i5ctdfzmiubdsml6ye/testapp/_uploads/11ddb28e-04d9-4a9e-b1aa-c7a3df5455ac/data
    [yyyy-mm-dd hh:mm:ss CET]     0B registry/docker/registry/v2/repositories/e2e-1545143177-hqaqbs55i5ctdfzmiubdsml6ye/testapp/_uploads/32137e45-7dd3-40a0-9223-466d31934d80/data
    [yyyy-mm-dd hh:mm:ss CET]     0B registry/docker/registry/v2/repositories/e2e-1545143177-hqaqbs55i5ctdfzmiubdsml6ye/testapp/_uploads/354a1b6a-8df2-491c-b26e-00df1ebf5888/data
    
  • The incomplete uploads are not cleaned. Currently, the incomplete multipart have to be deleted manually. If incomplete uploads get too many in s3 storage, the docker push does stop working with the HTTP error 500.

Environment

  • OpenShift Container Platform (OCP)
    • v3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content