Project

General

Profile

Actions
Copy link

Bug #23939

open

etag/hash and content_type fields were concatenated wit \u0000

Added by Syed Armani about 6 years ago. Updated almost 6 years ago.

Status:
Triaged
Priority:
Normal
Assignee:
Orit Wasserman
Target version:
Ceph - v12.2.2
% Done:

0%

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

Description

We are running radosgw(Luminous) with Swift API enabled. We observed
that after updating an object the "hash" and "content_type"
fields were concatenated with "\u000".

Steps to reproduce the issue.

[1] Create a container(Swift nomenclature)
 [2] Upload a file with "swift --debug upload <name-of-container> <filename>" 
 [3] Make a change to the file.
 [4] Update with "swift --debug post <container-name> <filename>" 
 [5] List again with "swift --debug list <container>"

After step 5, the RESP BODY is like this:

{
    "bytes": 251,
    "content_type": "text/plain\u0000",
    "hash": "8df6558bcaed354cbf24aa3b4a790fad\u0000",
    "last_modified": "2018-04-23T06:21:52.574Z",
    "name": "test.txt" 
}

As you can see there is a "\u0000" character in both "content_type" and "hash" fields.

Also, when we used the "radosgw-admin object stat" we observed this:

  1. diff beforeUpdate.txt afterUpdate.txt
    39c39
    < "tag": "7626b755-713f-4be3-9062-9328ad3fa425.6729.9",
    ---

"tag": "_GmhB3jfJWOV7yxkzk0GdrL_8Z71pVN7",

79,80c79
< "user.rgw.tail_tag": "7626b755-713f-4be3-9062-9328ad3fa425.6729.9",
< "user.rgw.x-amz-meta-mtime": "1524468290.332091"
---

"user.rgw.tail_tag": "7626b755-713f-4be3-9062-9328ad3fa425.6729.9"

Please note that the "tag" field changed after update and "user.rgw.x-amz-meta-mtime" disappeared.

beforeUpdate.txt --> http://paste.openstack.org/show/719723/
afterUpdate.txt --> http://paste.openstack.org/show/719724/

We are using a combination of native swift clusters and radsogw based swift clusters.
Our ambition is to switch to radosgw completely. At the moment issues like above are
breaking clients which are not able to parse information because of the presence of
extra "\u0000" character. We donot see any such issue with the native Swift clusters.

Actions
Copy link

Also available in: Atom PDF