Bug #1698
closedradosgw-admin log list returns invalid json when a log object was created with a name that contains invalid utf-8
0%
Description
2011-11-07-12-0-<80>..
Updated by Matthew Wodrich over 12 years ago
The description above is malformed for whatever reason, so I'll try again:
radosgw-admin log list is producing bad JSON containing invalid utf-8.
Running this command on peon1560:
perl -e "use JSON::XS; \$loglist = \`radosgw-admin log list --date=2011-11-07 --format=json\`; @decodedloglist = decode_json(\$loglist); print scalar @decodedloglist;"
Yields this error:
malformed UTF-8 character in JSON string, at character offset 432651 (before "...","2011-11-07-10-...") at -e line 1.
Due to the log name showing in the description.
Updated by Matthew Wodrich over 12 years ago
The two preceding days show similar errors as well.
Updated by Sage Weil over 12 years ago
- Target version set to v0.39
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 979
Updated by Anonymous over 12 years ago
This is my vote for "let's not allow radosgw clients to create artifacts with non-utf8 names in the first place".
Updated by Yehuda Sadeh over 12 years ago
- Status changed from New to Resolved
Fixed, commit:2e195500b5d3a8ab8512bcf2a219a6b7ff922c97. Not logging entries with non-utf8 bucket name.
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22) - Target version deleted (
v0.39)
Bulk reassign of radosgw category to RGW project.