-
Bug
-
Resolution: Done
-
Blocker
-
Pipelines 1.9.1
-
None
-
False
-
None
-
False
-
OpenShift Pipelines 1.9.1 release introduced an OLM misconfiguration that blocks OCP cluster upgrade; this misconfiguration is fixed in this issue
-
-
Description of problem:
we have a cluster at 4.11.25 which we wanted to upgrade to 4.12, but we see this:
Cluster operator operator-lifecycle-manager should not be upgraded between minor versions: ClusterServiceVersions blocking cluster upgrade: openshift-operators/openshift-pipelines-operator-rh.v1.9.1 has invalid olm.maxOpenShiftVersion properties: failed to parse "{"version":"4.13"}" as semver: Invalid character(s) found in major number "0{\"version\":\"4"
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
we started with pipelines 1.7, then 1.8.2, then 1.9.0, then 1.9.1 ... and now wanted to update OCP to 4.12
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Build Details:
Additional info (Such as Logs, Screenshots, etc):
- relates to
-
OCPBUGS-9928 sdk bundle validate does not validate the maxocpversion field when set
- Closed
-
OCPBUGS-9932 sdk bundle validate does not validate the maxocpversion field when set
- Closed
-
RHDEVDOCS-5033 Pipelines 1.9.2 Release Notes
- Closed