-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Some operator has maxVersion set. For example, OpenShift Logging Operator v6.1 only support maximum OCP 4.18. This operator will block the upgrade to 4.19 (as in screenshot).
However, the cluster shall aware of this maxVersion would block the upgrade, and just refuse to upgrade at the first place, rather than stucking in the middle of upgrading.
Version-Release number of selected component (if applicable):
OCP 4.19
How reproducible:
Install an OCP 4.18 cluster, install OpenShift Logging Operator v6.1, then set upgrade channel to candidate-4.19 and start upgrade
Steps to Reproduce:
1. Install OCP 4.18 cluster
2. Install OpenShift Logging Operator from Operator Hub with channel 6.1
3. Set upgrade channel of the cluster to candidate-4.19
4. Start cluster upgrade
Actual results:
The cluster start to upgrade. Some component will upgrade to 4.19, while the overall upgrade is blocked due to the maxVersion set for OpenShift Logging Operator
Expected results:
Upgrade was refused
Additional info:
