Known Issues for Object Storage
These known issues have been identified in Object Storage.
PAR creation can fail when using long object names
- Details
- Creating a pre-authenticated request (PAR) can fail when using long object names, resulting in a 500: Internal Server Error error. This failure is because of the size of the metadata associated with longer object names.
- Workaround
- Use shorter object names. The limit depends on implementation-specific details related to the user creating the PAR, so we can't currently give an exact limit. See Pre-Authenticated Requests for more information on that feature.
Uncommitted or failed multipart uploads in destination bucket
- Details
- Lingering uncommitted or failed multipart uploads might occur in replication destination buckets. You can't use the OCI Console or Object Storage Object Lifecycle Management to delete the uncommitted or failed multipart upload parts on a destination bucket.
- Workaround
- Use the Object Storage CLI, the documented bash script at Deleting a Multipart Upload from Object Storage, or use a supported SDK using the AbortMultipartUpload API, such as python, to abort and remove the uncommitted or failed multipart upload parts.