Bug #41146
closed
rgw: rgw-log issues the wrong message when decompression fails
Added by Fengzhe Han over 4 years ago.
Updated over 3 years ago.
Backport:
luminous mimic nautilus
Description
ceph version：14.2.2
The zlib compression takes effect in RGW。
When getting objects failed because of decompress-failed。“ceph-client.rgw” log printed “Compression failed with exit code”，I think it should be “deCompression failed with exit code......”。
ORIGINAL TITLE: nautilus RGW ： When decompression failed，rgw-log print “Compression failed with exit code ......”。The log should be “deCompression failed with exit code ......”
Would you be willing to submit a patch for this
Abhishek Lekshmanan wrote:
Would you be willing to submit a patch for this
Yes.I am glad to submit a patch for this.
- Status changed from New to Pending Backport
- Tags set to compression
- Backport set to luminous mimic nautilus
- Pull request ID set to 29633
- Copied to Backport #41270: mimic: rgw: rgw-log issues the wrong message when decompression fails added
- Copied to Backport #41271: luminous: rgw: rgw-log issues the wrong message when decompression fails added
- Copied to Backport #41272: nautilus: rgw: rgw-log issues the wrong message when decompression fails added
- Subject changed from nautilus RGW ： When decompression failed，rgw-log print “Compression failed with exit code ......”。The log should be “deCompression failed with exit code ......” to rgw: rgw-log issues the wrong message when decompression fails
- Description updated (diff)
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF