Bug 1339256

Summary: [RFE] rgw : support size suffixes for --max-size in radosgw-admin command
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: RGWAssignee: Orit Wasserman <owasserm>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact:
Priority: high    
Version: 1.3.2CC: cbodley, ceph-eng-bugs, hnallurv, icolle, kbader, kdreyer, mbenjamin, owasserm, sweil, uboppana, vashastr
Target Milestone: rcKeywords: FutureFeature
Target Release: 2.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.3-2.el7cp Ubuntu: ceph_10.2.3-3redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-22 19:25:55 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:

Description Vikhyat Umrao 2016-05-24 13:43:55 UTC 
Description of problem:
rgw : support size suffixes for --max-size in radosgw-admin command 

Upstream RFE link : http://tracker.ceph.com/issues/16004

# radosgw-admin --help
usage: radosgw-admin <cmd> [options...]
[...]

Quota options:
   --bucket                  specified bucket for quota command
   --max-objects             specify max objects (negative value to disable)
   --max-size                specify max size (in bytes, negative value to disable) <------------
   --quota-scope             scope of quota (bucket, user)

- Currently `--max-size` only takes size in bytes.



Version-Release number of selected component (if applicable):
Red Hat Ceph Storage 1.3.2
Comment 5 Vikhyat Umrao 2016-05-24 17:47:25 UTC 
Upstream patch : https://github.com/ceph/ceph/pull/9297
Comment 8 Vikhyat Umrao 2016-06-16 07:18:34 UTC 
Upstream Jewel Backport Tracker : http://tracker.ceph.com/issues/16339
Upstream Jewel Backport PR : https://github.com/ceph/ceph/pull/9743
Comment 13 errata-xmlrpc 2016-11-22 19:25:55 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://rhn.redhat.com/errata/RHSA-2016-2815.html