-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The source cr ClusterLogSubscription.yaml in github sets the CLO channel to stable-6.0. This needs to be updated to stable-6.1 otherwise the CLO operator will not deploy on OCP 4.18 and 4.19 Current workaround is to override the CLO subscription channel when using the above CRD https://github.com/openshift-kni/cnf-features-deploy/blob/master/ztp/source-crs/ClusterLogSubscription.yaml#L9
Version-Release number of selected component (if applicable):
source-crs for OCP 4.18 and 4.19
How reproducible:
always
Steps to Reproduce:
1.deploy SNO using the current RAN Telco DU profile using the existing source-crs in the ZTP container 2. observe CLO subscription 3.
Actual results:
Deployment of CLO operator fails due to stable-6.0 not present in operator index
Expected results:
Deployment of CLO operator should succeed with the right channel specific (stable-6.1)
Additional info:
- is duplicated by
-
OCPBUGS-54718 Cluster Compare - Cluster Logging template points to stable-6.1 instead of stable-6.2
-
- Closed
-
- is related to
-
OCPBUGS-60864 [4.19 RAN RDS] cluster logging 6.1 doesn't exist in 4.19 cnf-features-deploy
-
- Closed
-
-
OCPBUGS-50528 Cluster Logging - Source CRs are pointing to CLO 6.0 for 4.18 and master
-
- Closed
-
- links to
-
RHEA-2025:145129 OpenShift Container Platform 4.19.0 CNF vRAN extras update
- mentioned on
(6 mentioned on)