Bug 2037241 - default TTL for noobaa cache buckets should be 0
Summary: default TTL for noobaa cache buckets should be 0
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Sanjal Katiyar
QA Contact: Parikshith
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-05 10:26 UTC by Danny
Modified: 2022-03-10 16:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10861 0 None open Bug 2037241: Default cache ns store ttl to 0 2022-01-17 13:33:49 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:23 UTC

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.


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