Actions
Bug #49405
closedS3 create bucket should not do response in json
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
RGW s3 cannot work with AWS sdk s3 client on node.js, due to create bucket returns json instead of xml.
AWS S3 client message:
{ XMLParserError: Non-whitespace before first tag. Line: 0 Column: 1 Char: { at error (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/sax/lib/sax.js:667:10) at strictFail (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/sax/lib/sax.js:693:7) at beginWhiteSpace (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/sax/lib/sax.js:967:7) at SAXParser.write (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/sax/lib/sax.js:1019:11) at Parser.exports.Parser.Parser.parseString (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/xml2js/lib/parser.js:322:31) at Parser.parseString (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/xml2js/lib/parser.js:5:59) at NodeXmlParser.parse (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/aws-sdk/lib/xml/node_parser.js:31:10) at Request.extractData (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/aws-sdk/lib/protocol/rest_xml.js:97:23) at Request.callListeners (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/home/ignas/Dokumentai/cloudityo-v2/backend/libs/cloudityo-tools/node_modules/aws-sdk/lib/sequential_executor.js:78:10) message: 'Non-whitespace before first tag.\nLine: 0\nColumn: 1\nChar: {', code: 'XMLParserError', retryable: true, time: 2021-02-21T20:23:25.533Z, statusCode: 200 }
Issue seems to be reported in v9.2.1 issue#18889, fixed in v11.2.1 pr#13875
Actions