Bug 1753000 - Segmentation fault in radosgw-admin bucket reshard command
Summary: Segmentation fault in radosgw-admin bucket reshard command
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z1
: 3.3
Assignee: Casey Bodley
QA Contact: RUDRA PRATAP
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 18:28 UTC by Uday kurundwade
Modified: 2023-03-24 15:27 UTC (History)
12 users (show)

Fixed In Version: RHEL: ceph-12.2.12-71.el7cp Ubuntu: ceph_12.2.12-64redhat1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 13:29:30 UTC
Embargoed:


Attachments (Terms of Use)
Attached file of error message (13.58 KB, text/plain)
2019-09-17 18:28 UTC, Uday kurundwade
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3173 0 None None None 2019-10-22 13:29:46 UTC

Description Uday kurundwade 2019-09-17 18:28:14 UTC
Created attachment 1615960 [details]
Attached file of error message

Description of problem:
Getting segmentation fault error message after executing manual reshard command

Version-Release number of selected component (if applicable):
ceph-common-12.2.12-70.el7cp.x86_64
ceph-mon-12.2.12-70.el7cp.x86_64
ceph-base-12.2.12-70.el7cp.x86_64
ceph-radosgw-12.2.12-70.el7cp.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Deploy 3.3 cluster with RGW
2.Create bucket and write some data
3.Run manual reshard command (radosgw-admin bucket reshard --bucket=mybucket1 --num-shards=10)


Actual results:
Getting segmentation fault error

Expected results:
Command should do re sharding without throwing error

Additional info:

Comment 17 errata-xmlrpc 2019-10-22 13:29:30 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, 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/RHBA-2019:3173


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