Object Storage Service:What do I do if an error that indicates parts failed to be deleted in the OSS console is reported?

Description and solutions

1. Collect the Form Data and Preview results after you call the abort_multi_part_uploads.json operation when the parts are deleted in the OSS console.

2. The preceding figure shows that the error is a frontend error, and you can obtain the corresponding request ID.

3. You can use the request ID to obtain the following error message. The error message is returned because the object name does not meet the requirements.

   [java.lang.IllegalArgumentException: The object key is invalid. An object name should be 
   between 1 - 1023 bytes long when encoded as UTF-8 and cannot contain LF or CR or 
   unsupported charts in XML1.0.]

4. Analyze the name of the part. The Object Name of the part starts with a forward slash (/). However, the request is not sent to the backend because the request is limited in the console.

   {
     "region": [
       "oss-cn-XXXX"
     ],
     "objectName": [
       "/2017-02-22/bk.XXXX_r_bj.2017-02-22.gz,/2017-04-01/bk.XXXX_r_bj.2017-04-01.gz"
     ],
     "uploadId": [
       "5557BCXXXXXXXXXXC6206E6,F23072A1DXXXXXXXXXXXX8D2D3499"
     ],
     "bucketName": [
       "redisXXXXkup"
     ]
   }

5. The OSS console and specific OSS SDKs, such as OSS SDK for Java, have limits on the validity of object parameters. Therefore, an error is reported for abnormal parameters. Such objects must be deleted by using specific tools or API operations.

   Note

   You can use tools that do not have limits on the validity of parameters, such as ossutil or osscmd, to delete abnormal objects.