-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19.z, 4.20.0, 4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-60285. The following is the description of the original issue:
—
Description of problem:
When deploying the telco-hub with the logging operator enabled, we see the below error in ArgoCD.
The Kubernetes API could not find observability.openshift.io/ClusterLogForwarder for requested resource openshift-logging/instance. Make sure the "ClusterLogForwarder" CRD is installed on the destination cluster.
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Always (when deploying the telco-hub pattern with logging components enabled)
Steps to Reproduce:
1. Deploy the telco-cluster as defined in https://github.com/openshift-kni/telco-reference/tree/main 2. Enbale logging operator in your kustomize
Actual results:
ArgoCD stuck deploying the telco-hub.
Expected results:
telco-hub fully deployed and properly configured.
Additional info:
- clones
-
OCPBUGS-60285 [telco-hub] ClusterLogForwarder CRD Not Found - Missing Logging Operator Dependencies in Telco Hub Pattern
-
- Verified
-
- is blocked by
-
OCPBUGS-60285 [telco-hub] ClusterLogForwarder CRD Not Found - Missing Logging Operator Dependencies in Telco Hub Pattern
-
- Verified
-
- links to