Bug 1929242 - [GSS] [RFE] QoS and limits in Object Bucket Claims in OpenShift for RGW
Summary: [GSS] [RFE] QoS and limits in Object Bucket Claims in OpenShift for RGW
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ODF 4.9.0
Assignee: Jose A. Rivera
QA Contact: Parikshith
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 14:30 UTC by amansan
Modified: 2023-12-08 04:25 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.QoS and limits in Object Bucket Claims in OpenShift for RGW With this update, you can set a limit to the size of the object count in the object bucket claim (OBC) custom resource definition (CRD) to avoid over consumption of the storage by applications.
Clone Of:
Environment:
Last Closed: 2021-12-13 17:44:30 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:5086 0 None None None 2021-12-13 17:44:43 UTC

Comment 8 Mudit Agarwal 2021-09-27 06:13:23 UTC
Thanks Jiffin, moving it to ON_QA as it is covered in https://issues.redhat.com/browse/RHSTOR-1967

Comment 13 Mudit Agarwal 2021-11-03 03:49:42 UTC
Please add the doc text

Comment 17 errata-xmlrpc 2021-12-13 17:44: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 (Moderate: Red Hat OpenShift Data Foundation 4.9.0 enhancement, security, and bug fix 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-2021:5086

Comment 18 Red Hat Bugzilla 2023-12-08 04:25:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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