Bug 1753000

Summary: Segmentation fault in radosgw-admin bucket reshard command
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Uday kurundwade <ukurundw>
Component: RGWAssignee: Casey Bodley <cbodley>
Status: CLOSED ERRATA QA Contact: RUDRA PRATAP <rpratap>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3CC: bancinco, cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, racpatel, rpratap, sweil, tchandra, tserlin, vumrao
Target Milestone: z1Keywords: Regression
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.12-71.el7cp Ubuntu: ceph_12.2.12-64redhat1 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 13:29:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Attached file of error message none

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