Bug 2358825 - Modify Bandwidth and IOPS limits for QoS commands
Summary: Modify Bandwidth and IOPS limits for QoS commands
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 8.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: 8.1
Assignee: Shweta Bhosale
QA Contact: Manisha Saini
URL:
Whiteboard:
: 2359054 (view as bug list)
Depends On:
Blocks: 2359671 2359054 2359055 2359676 2359677 2359678
TreeView+ depends on / blocked
 
Reported: 2025-04-10 11:37 UTC by Naresh
Modified: 2025-06-26 12:24 UTC (History)
6 users (show)

Fixed In Version: ceph-19.2.1-133.el9cp
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2359054 2359055 2359671 2359676 2359677 2359678 (view as bug list)
Environment:
Last Closed: 2025-06-26 12:23:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-11123 0 None None None 2025-04-10 11:39:14 UTC
Red Hat Product Errata RHSA-2025:9775 0 None None None 2025-06-26 12:24:06 UTC

Description Naresh 2025-04-10 11:37:57 UTC 
Description of problem:Update the limits of QoS bandwidth and IOPs limits.


Version-Release number of selected component (if applicable):


How reproducible: Run any QoS Ceph adm commands for QoS


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

New Limit values for bandwidth and IOPS should be

Bandwidth:  Minimum 1MBPS  and maximum  100GBPS
IOPS. :     Minimum 10     and maximum 409600  




Additional info:
Comment 7 errata-xmlrpc 2025-06-26 12:23:39 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 (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), 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-2025:9775
Note You need to log in before you can comment on or make changes to this bug.