Project

General

Profile

Actions

Bug #21560

closed

rgw: put cors operation returns 500 unknown error (ops are ECANCELED)

Added by Vaibhav Bhembre over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Performing PUT /?cors requests on a RGW endpoint results in 500 UnknownError when using a generic command line tool like s3cmd.

The RGW daemon log has the following line in it:

2017-09-26 16:52:20.189944 7efe947f0700  1 -- 10.74.46.11:0/3954610334 <== osd.6 10.74.45.142:6800/16037 661008 ==== osd_op_reply(37516507 .bucket.meta.vdbbucket:76bcb3c5-9013-4817-8e0b-9ec86fa9a561.25665.4 [delete,create 0~0,call,call,writefull 0~335,setxattr (133),setxattr (96)] v0'0 uv0 ondisk = -125 ((125) Operation canceled)) v7 ==== 437+0+0 (2039141977 0 0) 0x7efc880a0ca0 con 0x7eff30090960

The CORS xml looks like follows:

<CORSConfiguration>
<CORSRule>
    <ID>example.com: Allow GET with S3</ID>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <AllowedHeader>*</AllowedHeader>
    <ExposeHeader>ETag</ExposeHeader>
    <MaxAgeSeconds>1800</MaxAgeSeconds>
</CORSRule>
</CORSConfiguration>

And the command to setcors looks like follows:

s3cmd setcors cors.xml s3://vdbbucket

The bucket stats of the bucket look like follows:

{
    "bucket": "vdbbucket",
    "pool": "default.rgw.buckets.data",
    "index_pool": "default.rgw.buckets.index",
    "id": "76bcb3c5-9013-4817-8e0b-9ec86fa9a561.25665.4",
    "marker": "76bcb3c5-9013-4817-8e0b-9ec86fa9a561.25665.4",
    "owner": "vdb",
    "ver": "0#722",
    "master_ver": "0#0",
    "mtime": "2017-09-26 14:53:36.389247",
    "max_marker": "0#",
    "usage": {
        "rgw.main": {
            "size_kb": 111723,
            "size_kb_actual": 112296,
            "num_objects": 298
        },
        "rgw.multimeta": {
            "size_kb": 0,
            "size_kb_actual": 0,
            "num_objects": 0
        }
    },
    "bucket_quota": {
        "enabled": false,
        "max_size_kb": -1,
        "max_objects": -1
    }
}

I have attached the complete RGW log with this tracker for this request. Please let me know if there's anything else I can provide to help. It would also help to know if there's any temporary workaround I can have in place to re-enable CORS requests since they seem broken temporarily.


Files

ceph-client.rgw.log (7.94 KB) ceph-client.rgw.log Vaibhav Bhembre, 09/26/2017 06:14 PM

Related issues 3 (0 open3 closed)

Related to rgw - Bug #22517: Cache never becoming consistent after failed updatesResolvedAdam Emerson12/20/2017

Actions
Copied to rgw - Backport #22588: luminous: rgw: put cors operation returns 500 unknown error (ops are ECANCELED)ResolvedAdam EmersonActions
Copied to rgw - Backport #22589: jewel: rgw: put cors operation returns 500 unknown error (ops are ECANCELED)ResolvedMatt BenjaminActions
Actions

Also available in: Atom PDF