Details
-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.12.0, 4.11.z, 4.10.z, 4.9.z, 4.8.z
-
Low
-
X-Files 232
-
1
-
Rejected
-
False
-
Description
Description of problem:
I found OLM version is 0.17.0 for OCP 4.6, 4.7, 4.8, see:
OLM version is 0.18.3 for OCP 4.9, https://github.com/openshift/operator-framework-olm/blob/release-4.9/staging/operator-lifecycle-manager/OLM_VERSION
OLM version is 0.19.0 for OCP 4.10, 4.11, 4.12
It's unclear to the user. What's the version naming rule we should follow? Thanks!
Version-Release number of selected component (if applicable):
4.6 -> 4.12
How reproducible:
always
Steps to Reproduce:
1. Check the OLM version MacBook-Pro:operator-framework-olm jianzhang$ oc exec catalog-operator-7f4f564c97-fvzl4 -- olm --version OLM version: 0.19.0 git commit: 11644a5433442c33698d2eee8d3f865b0d9386c0 MacBook-Pro:operator-framework-olm jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.12.0-0.nightly-2022-08-31-101631 True False 9h Error while reconciling 4.12.0-0.nightly-2022-08-31-101631: authentication, kube-controller-manager, machine-config, openshift-apiserver has an unknown error: ClusterOperatorsDegraded
Actual results:
see above desciption.
Expected results:
OLM version should follow a clear version naming rule to align with OCP version.
Additional info: