Bug 2100967 - [rfe] translate radosgw-admin 2002 to ENOENT (POSIX); was: radosgw-admin bucket stats returns Unknown error 2002
Summary: [rfe] translate radosgw-admin 2002 to ENOENT (POSIX); was: radosgw-admin buck...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 4.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 5.2
Assignee: Matt Benjamin (redhat)
QA Contact: Vidushi Mishra
Akash Raj
URL:
Whiteboard:
Depends On: 2089220
Blocks: 2100966 2102272
TreeView+ depends on / blocked
 
Reported: 2022-06-24 19:41 UTC by Vikhyat Umrao
Modified: 2022-08-09 17:39 UTC (History)
15 users (show)

Fixed In Version: ceph-16.2.7-63.el8cp
Doc Type: Bug Fix
Doc Text:
.Result code 2002 of `radosgw-admin` commands is explicitly translated to 2 Previously, a change in the S3 error translation of i1nternal `NoSuchBucket` result inadvertently changed the error code from the `radosgw-admin bucket stats` command causing the the programs checking the shell result code of those `radosgw-admin` commands to see a different result code. With this fix, the result code 2002 is explicitly translated to 2 and users can see the original behaviour.
Clone Of: 2089220
Environment:
Last Closed: 2022-08-09 17:39:10 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4620 0 None None None 2022-06-24 19:42:34 UTC
Red Hat Product Errata RHSA-2022:5997 0 None None None 2022-08-09 17:39:56 UTC

Comment 10 errata-xmlrpc 2022-08-09 17:39:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5997


Note You need to log in before you can comment on or make changes to this bug.