Bug 2037241

Summary: default TTL for noobaa cache buckets should be 0
Product: OpenShift Container Platform Reporter: Danny <dzaken>
Component: Console Storage PluginAssignee: Sanjal Katiyar <skatiyar>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: high Docs Contact:
Priority: high    
Version: 4.10CC: afrahman, aos-bugs, etamir, jefbrown, madam, mmuench, nbecker, nthomas, ocs-bugs, skatiyar
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:37:09 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:

Description Danny 2022-01-05 10:26:05 UTC
Description of problem (please be detailed as possible and provide log

following https://bugzilla.redhat.com/show_bug.cgi?id=2024107 it was decided that it makes more sense to use a default TTL of 0 for cache buckets. 
this was changed internally in noobaa, but should also be changed in the management console

Version of all relevant components (if applicable):

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Is there any workaround available to the best of your knowledge?

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

Can this issue reproducible?

Can this issue reproduce from the UI?

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 9 errata-xmlrpc 2022-03-10 16:37:09 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: OpenShift Container Platform 4.10.3 security 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.