-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.20.z
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-65804. The following is the description of the original issue:
—
Description of problem:
The log in the console backend will print out this error: failed to get new config for olm client
Version-Release number of selected component (if applicable):
4.21
How reproducible:
Always
Steps to Reproduce:
1. Build the backend and run it
2. Visit the console with kubeadmin
3. Read the backend log
Actual results:
... failed to get new config for olm client ...
Expected results:
No error should be printed out
Additional info:
https://github.com/openshift/console/blob/main/pkg/olm/handler.go#L112 Here we are always passing the nil.
- clones
-
OCPBUGS-65804 Console backend showing failed to get new config for olm client error
-
- Verified
-
- is blocked by
-
OCPBUGS-65804 Console backend showing failed to get new config for olm client error
-
- Verified
-
- links to