-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
Rejected
-
None
-
In Progress
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
If operator-controller's cluster catalog controller makes a request to Catalogd in order to cache a catalog, and it receives an error making that request, it caches that error. All subsequent retries will fetch that error from the cache and not actually attempt to populate the cache again until the catalog ref changes.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-20-085127
How reproducible:
Not often or easy, depends on a race condition between operator-controller reading its cache of ClusterCatalog objects and Catalogd populating (or removing) the served catalog contents
Steps to Reproduce:
1. 2. 3.
Actual results:
Operator controller doesn't recover from failed cache attempt until catalog has a new resolved reference
Expected results:
Operator controller should attempt to populate the cache again for an existing reference if the cached result is an error from a previous attempt.
Additional info:
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update